apply commit 61cc4534b655 ("locking/lockdep: Avoid potential access of invalid memory in lock_class") to linux-5.4-stable
Hi Reviewers,
This patch fixes a use-after-free error when /proc/lockdep is read by user after a lockdep splat.
I checked and I think this patch can be applied to stable-5.4 and later.
commit: 61cc4534b6550997c97a03759ab46b29d44c0017 Subject: locking/lockdep: Avoid potential access of invalid memory in lock_class
Thanks. Cheng-Jui Wang
On Wed, Mar 16, 2022 at 02:01:12PM +0800, Cheng Jui Wang wrote:
Hi Reviewers,
This patch fixes a use-after-free error when /proc/lockdep is read by user after a lockdep splat.
I checked and I think this patch can be applied to stable-5.4 and later.
commit: 61cc4534b6550997c97a03759ab46b29d44c0017 Subject: locking/lockdep: Avoid potential access of invalid memory in lock_class
I do not see that commit id in Linus's tree, are you sure it is correct?
thanks,
greg k-h
On 2022/03/16 23:26, Greg KH wrote:
On Wed, Mar 16, 2022 at 02:01:12PM +0800, Cheng Jui Wang wrote:
Hi Reviewers,
This patch fixes a use-after-free error when /proc/lockdep is read by user after a lockdep splat.
I checked and I think this patch can be applied to stable-5.4 and later.
commit: 61cc4534b6550997c97a03759ab46b29d44c0017 Subject: locking/lockdep: Avoid potential access of invalid memory in lock_class
I do not see that commit id in Linus's tree, are you sure it is correct?
It is in linux-next.git, and will be sent to linux.git when next merge window opens.
On 3/16/22 10:26, Greg KH wrote:
On Wed, Mar 16, 2022 at 02:01:12PM +0800, Cheng Jui Wang wrote:
Hi Reviewers,
This patch fixes a use-after-free error when /proc/lockdep is read by user after a lockdep splat.
I checked and I think this patch can be applied to stable-5.4 and later.
commit: 61cc4534b6550997c97a03759ab46b29d44c0017 Subject: locking/lockdep: Avoid potential access of invalid memory in lock_class
I do not see that commit id in Linus's tree, are you sure it is correct?
This commit is currently in the tip tree. It have not been merged into the mainline yet, though it should happen in the upcoming merge window.
Cheers, Longman
On Wed, Mar 16, 2022 at 10:38:04AM -0400, Waiman Long wrote:
On 3/16/22 10:26, Greg KH wrote:
On Wed, Mar 16, 2022 at 02:01:12PM +0800, Cheng Jui Wang wrote:
Hi Reviewers,
This patch fixes a use-after-free error when /proc/lockdep is read by user after a lockdep splat.
I checked and I think this patch can be applied to stable-5.4 and later.
commit: 61cc4534b6550997c97a03759ab46b29d44c0017 Subject: locking/lockdep: Avoid potential access of invalid memory in lock_class
I do not see that commit id in Linus's tree, are you sure it is correct?
This commit is currently in the tip tree. It have not been merged into the mainline yet, though it should happen in the upcoming merge window.
As per the stable kernel rules, the commit has to be in Linus's tree first. Please email us again when that has happened.
thanks,
greg k-h
linux-stable-mirror@lists.linaro.org
-
Cheng Jui Wang -
Greg KH -
Tetsuo Handa -
Waiman Long