From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alexey Khoroshilov <khoroshilov@ispras.ru>
Cc: stable@vger.kernel.org,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
ldv-project@linuxtesting.org
Subject: Re: [PATCH 5.10 0/1] Backport support for tracing capacity constants
Date: Fri, 12 Aug 2022 18:45:04 +0200 [thread overview]
Message-ID: <YvaDkDyy2eohvkmx@kroah.com> (raw)
In-Reply-To: <97dd7ee5-e81b-30d3-b38b-ba39159af823@ispras.ru>
On Fri, Aug 12, 2022 at 07:01:55PM +0300, Alexey Khoroshilov wrote:
> On 12.08.2022 18:37, Greg Kroah-Hartman wrote:
> > On Fri, Aug 12, 2022 at 01:08:02AM +0300, Alexey Khoroshilov wrote:
> >> Syzkaller reports a number of "BUG: MAX_LOCKDEP_CHAINS too low!" warnings
> >> on 5.10 branch and it means that the fuzz testing is terminated prematurely.
> >> Since upstream patch that allows to increase limits is applied cleanly
> >> and our testing demonstrated that it works well, we suggest to backport
> >> it to the 5.10 branch.
> >
> > What about all of the newer kernels branches, it is needed in 5.15.y,
> > 5.18.y and 5.19.y, right? What's so special about 5.10.y?
>
>
> The commit was introduced in 5.13, so it is already there.
>
> By the way, I messed up upstream commit id in my message, sorry about that.
>
> The correct one:
> 5dc33592e95534dc8455ce3e9baaaf3dae0fff82
Ah, that makes more sense, the id you gave me was not in a released
kernel yet...
prev parent reply other threads:[~2022-08-12 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 22:08 [PATCH 5.10 0/1] Backport support for tracing capacity constants Alexey Khoroshilov
2022-08-11 22:08 ` [PATCH 5.10 1/1] lockdep: Allow tuning " Alexey Khoroshilov
2022-08-12 15:37 ` [PATCH 5.10 0/1] Backport support for " Greg Kroah-Hartman
2022-08-12 16:01 ` Alexey Khoroshilov
2022-08-12 16:45 ` Greg Kroah-Hartman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YvaDkDyy2eohvkmx@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=khoroshilov@ispras.ru \
--cc=ldv-project@linuxtesting.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox