[<prev] [next>] [day] [month] [year] [list]
Message-ID: <YkLtF5m86AVdUkwn@kroah.com>
Date: Tue, 29 Mar 2022 13:27:19 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: linux-kernel@...r.kernel.org
Cc: 77f05c15-81b6-bddd-9650-80d5f23fe330@...ove.sakura.ne.jp,
bvanassche@....org, cheng-jui.wang@...iatek.com,
longman@...hat.com, penguin-kernel@...ove.sakura.ne.jp,
peterz@...radead.org, stable-commits@...r.kernel.org
Subject: Re: Patch "locking/lockdep: Avoid potential access of invalid memory
in lock_class" has been added to the 5.4-stable tree
On Tue, Mar 29, 2022 at 01:23:38PM +0200, gregkh@...uxfoundation.org wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> locking/lockdep: Avoid potential access of invalid memory in lock_class
>
> to the 5.4-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
> locking-lockdep-avoid-potential-access-of-invalid-memory-in-lock_class.patch
> and it can be found in the queue-5.4 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@...r.kernel.org> know about it.
Oops, nope, this breaks the build in 5.4.y.
Cheng-Jui, if you want this in 5.4.y, please provide a working backport.
thanks,
greg k-h
Powered by blists - more mailing lists