[Bug 1956720] Re: Focal update: upstream stable patchset 2022-01-07

2022-02-07 Thread Launchpad Bug Tracker
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   Mon, 31 Jan 2022
17:45:20 +0200

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0330

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-22942

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23222

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-24122

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956720

Title:
  Focal update: upstream stable patchset 2022-01-07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956720/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956720] Re: Focal update: upstream stable patchset 2022-01-07

2022-01-20 Thread Timo Aaltonen
the fix was already in 5.15-rc1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956720

Title:
  Focal update: upstream stable patchset 2022-01-07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956720/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956720] Re: Focal update: upstream stable patchset 2022-01-07

2022-01-20 Thread Timo Aaltonen
simply because it's was never sent for stable

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: Incomplete => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956720

Title:
  Focal update: upstream stable patchset 2022-01-07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956720/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956720] Re: Focal update: upstream stable patchset 2022-01-07

2022-01-20 Thread Stefan Metzmacher
Why is this commit not included here?

commit f95dc207b93da9c88ddbb7741ec3730c6657b88e
Author: Jens Axboe 
AuthorDate: Tue Aug 31 13:57:32 2021 -0600
Commit: Jens Axboe 
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 

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/195


** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: Fix Committed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956720

Title:
  Focal update: upstream stable patchset 2022-01-07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956720/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956720] Re: Focal update: upstream stable patchset 2022-01-07

2022-01-19 Thread Timo Aaltonen
** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: linux-oem-5.14 (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956720

Title:
  Focal update: upstream stable patchset 2022-01-07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956720/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs