* apply commit 61cc4534b655 ("locking/lockdep: Avoid potential access of invalid memory in lock_class") to linux-5.4-stable
@ 2022-03-16 6:01 ` Cheng Jui Wang
0 siblings, 0 replies; 10+ messages in thread
From: Cheng Jui Wang @ 2022-03-16 6:01 UTC (permalink / raw)
To: stable
Cc: Tetsuo Handa, Waiman Long, Peter Zijlstra (Intel),
Bart Van Assche, linux-mediatek, Eason-YH Lin
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* apply commit 61cc4534b655 ("locking/lockdep: Avoid potential access of invalid memory in lock_class") to linux-5.4-stable
@ 2022-03-16 6:01 ` Cheng Jui Wang
0 siblings, 0 replies; 10+ messages in thread
From: Cheng Jui Wang @ 2022-03-16 6:01 UTC (permalink / raw)
To: stable
Cc: Tetsuo Handa, Waiman Long, Peter Zijlstra (Intel),
Bart Van Assche, linux-mediatek, Eason-YH Lin
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
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: apply commit 61cc4534b655 ("locking/lockdep: Avoid potential access of invalid memory in lock_class") to linux-5.4-stable
2022-03-16 6:01 ` Cheng Jui Wang
@ 2022-03-16 14:26 ` Greg KH
-1 siblings, 0 replies; 10+ messages in thread
From: Greg KH @ 2022-03-16 14:26 UTC (permalink / raw)
To: Cheng Jui Wang
Cc: stable, Tetsuo Handa, Waiman Long, Peter Zijlstra (Intel),
Bart Van Assche, linux-mediatek, Eason-YH Lin
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: apply commit 61cc4534b655 ("locking/lockdep: Avoid potential access of invalid memory in lock_class") to linux-5.4-stable
@ 2022-03-16 14:26 ` Greg KH
0 siblings, 0 replies; 10+ messages in thread
From: Greg KH @ 2022-03-16 14:26 UTC (permalink / raw)
To: Cheng Jui Wang
Cc: stable, Tetsuo Handa, Waiman Long, Peter Zijlstra (Intel),
Bart Van Assche, linux-mediatek, Eason-YH Lin
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
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: apply commit 61cc4534b655 ("locking/lockdep: Avoid potential access of invalid memory in lock_class") to linux-5.4-stable
2022-03-16 14:26 ` Greg KH
@ 2022-03-16 14:30 ` Tetsuo Handa
-1 siblings, 0 replies; 10+ messages in thread
From: Tetsuo Handa @ 2022-03-16 14:30 UTC (permalink / raw)
To: Greg KH, Cheng Jui Wang
Cc: stable, Waiman Long, Peter Zijlstra (Intel),
Bart Van Assche, linux-mediatek, Eason-YH Lin
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.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: apply commit 61cc4534b655 ("locking/lockdep: Avoid potential access of invalid memory in lock_class") to linux-5.4-stable
@ 2022-03-16 14:30 ` Tetsuo Handa
0 siblings, 0 replies; 10+ messages in thread
From: Tetsuo Handa @ 2022-03-16 14:30 UTC (permalink / raw)
To: Greg KH, Cheng Jui Wang
Cc: stable, Waiman Long, Peter Zijlstra (Intel),
Bart Van Assche, linux-mediatek, Eason-YH Lin
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.
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: apply commit 61cc4534b655 ("locking/lockdep: Avoid potential access of invalid memory in lock_class") to linux-5.4-stable
2022-03-16 14:26 ` Greg KH
@ 2022-03-16 14:38 ` Waiman Long
-1 siblings, 0 replies; 10+ messages in thread
From: Waiman Long @ 2022-03-16 14:38 UTC (permalink / raw)
To: Greg KH, Cheng Jui Wang
Cc: stable, Tetsuo Handa, Peter Zijlstra (Intel),
Bart Van Assche, linux-mediatek, Eason-YH Lin
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: apply commit 61cc4534b655 ("locking/lockdep: Avoid potential access of invalid memory in lock_class") to linux-5.4-stable
@ 2022-03-16 14:38 ` Waiman Long
0 siblings, 0 replies; 10+ messages in thread
From: Waiman Long @ 2022-03-16 14:38 UTC (permalink / raw)
To: Greg KH, Cheng Jui Wang
Cc: stable, Tetsuo Handa, Peter Zijlstra (Intel),
Bart Van Assche, linux-mediatek, Eason-YH Lin
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
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: apply commit 61cc4534b655 ("locking/lockdep: Avoid potential access of invalid memory in lock_class") to linux-5.4-stable
2022-03-16 14:38 ` Waiman Long
@ 2022-03-16 15:31 ` Greg KH
-1 siblings, 0 replies; 10+ messages in thread
From: Greg KH @ 2022-03-16 15:31 UTC (permalink / raw)
To: Waiman Long
Cc: Cheng Jui Wang, stable, Tetsuo Handa, Peter Zijlstra (Intel),
Bart Van Assche, linux-mediatek, Eason-YH Lin
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: apply commit 61cc4534b655 ("locking/lockdep: Avoid potential access of invalid memory in lock_class") to linux-5.4-stable
@ 2022-03-16 15:31 ` Greg KH
0 siblings, 0 replies; 10+ messages in thread
From: Greg KH @ 2022-03-16 15:31 UTC (permalink / raw)
To: Waiman Long
Cc: Cheng Jui Wang, stable, Tetsuo Handa, Peter Zijlstra (Intel),
Bart Van Assche, linux-mediatek, Eason-YH Lin
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-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2022-03-16 15:33 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-03-16 6:01 apply commit 61cc4534b655 ("locking/lockdep: Avoid potential access of invalid memory in lock_class") to linux-5.4-stable Cheng Jui Wang
2022-03-16 6:01 ` Cheng Jui Wang
2022-03-16 14:26 ` Greg KH
2022-03-16 14:26 ` Greg KH
2022-03-16 14:30 ` Tetsuo Handa
2022-03-16 14:30 ` Tetsuo Handa
2022-03-16 14:38 ` Waiman Long
2022-03-16 14:38 ` Waiman Long
2022-03-16 15:31 ` Greg KH
2022-03-16 15:31 ` Greg KH
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.