Focal update: upstream stable patchset 2022-01-07

Bug #1956720 reported by Timo Aaltonen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-oem-5.14 (Ubuntu)
Invalid
Undecided
Unassigned
Focal
Fix Released
Undecided
Unassigned

Bug Description

    SRU Justification

    Impact:
       The upstream process for stable tree updates is quite similar
       in scope to the Ubuntu SRU process, e.g., each patch has to
       demonstrably fix a bug, and each patch is vetted by upstream
       by originating either directly from a mainline/stable Linux tree or
       a minimally backported form of that patch. The following upstream
       stable patches should be included in the Ubuntu kernel:

       upstream stable patchset 2022-01-07
       from git://git.kernel.org/

Timo Aaltonen (tjaalton)
Changed in linux-oem-5.14 (Ubuntu):
status: New → Confirmed
tags: added: kernel-stable-tracking-bug
Timo Aaltonen (tjaalton)
Changed in linux-oem-5.14 (Ubuntu Focal):
status: New → Fix Committed
Changed in linux-oem-5.14 (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Stefan Metzmacher (metze) wrote :

Why is this commit not included here?

commit f95dc207b93da9c88ddbb7741ec3730c6657b88e
Author: Jens Axboe <email address hidden>
AuthorDate: Tue Aug 31 13:57:32 2021 -0600
Commit: Jens Axboe <email address hidden>
CommitDate: Wed Sep 1 12:35:30 2021 -0600

    io-wq: split bounded and unbounded work into separate lists

    We've got a few issues that all boil down to the fact that we have one
    list of pending work items, yet two different types of workers to
    serve them. This causes some oddities around workers switching type and
    even hashed work vs regular work on the same bounded list.

    Just separate them out cleanly, similarly to how we already do
    accounting of what is running. That provides a clean separation and
    removes some corner cases that can cause stalls when handling IO
    that is punted to io-wq.

    Fixes: ecc53c48c13d ("io-wq: check max_worker limits if a worker transitions bound state")
    Signed-off-by: Jens Axboe <email address hidden>

Other io_uring related patches where backported here even without being
in linux-stable/linux-5.14.y. So why is this missing?

See also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952222

Changed in linux-oem-5.14 (Ubuntu Focal):
status: Fix Committed → Incomplete
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

simply because it's was never sent for stable

Changed in linux-oem-5.14 (Ubuntu Focal):
status: Incomplete → Fix Committed
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

the fix was already in 5.15-rc1

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24

---------------
linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium

  * focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP: #1959585)

  * Got black screen when resume from s2idle with AMD dGPU (LP: #1955790)
    - drm/amdgpu: don't do resets on APUs which don't support it

  * CVE-2022-0330
    - drm/i915: Flush TLBs before releasing backing store

  * CVE-2022-22942
    - SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy

  * CVE-2022-23222
    - bpf: Don't promote bogus looking registers after null check.
    - bpf, selftests: Add verifier test for mem_or_null register with offset.

  * CVE-2022-24122
    - ucount: Make get_ucount a safe get_user replacement

  * The display output on type-c hub doesn't work on ADL platform (LP: #1959061)
    - SAUCE: drm/i915/adlp: Fix TypeC PHY-ready status readout

 -- Timo Aaltonen <email address hidden> Mon, 31 Jan 2022 17:45:20 +0200

Changed in linux-oem-5.14 (Ubuntu Focal):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.