Peter, are you there? If you keep silence, we will assume that applying this patch is the way to go.
On 2021/03/20 16:34, Dmitry Vyukov wrote: > On Mon, Feb 8, 2021 at 11:29 AM Tetsuo Handa > <[email protected]> wrote: >> >> Since syzkaller continues various test cases until the kernel crashes, >> syzkaller tends to examine more locking dependencies than normal systems. >> As a result, syzbot is reporting that the fuzz testing was terminated >> due to hitting upper limits lockdep can track [1] [2] [3]. Since analysis >> via /proc/lockdep* did not show any obvious culprit [4] [5], we have no >> choice but allow tuning tracing capacity constants. >> >> [1] >> https://syzkaller.appspot.com/bug?id=3d97ba93fb3566000c1c59691ea427370d33ea1b >> [2] >> https://syzkaller.appspot.com/bug?id=381cb436fe60dc03d7fd2a092b46d7f09542a72a >> [3] >> https://syzkaller.appspot.com/bug?id=a588183ac34c1437fc0785e8f220e88282e5a29f >> [4] >> https://lkml.kernel.org/r/[email protected] >> [5] >> https://lkml.kernel.org/r/[email protected] >> >> Reported-by: syzbot <[email protected]> >> Reported-by: syzbot <[email protected]> >> Reported-by: syzbot <[email protected]> >> References: >> https://lkml.kernel.org/r/1595640639-9310-1-git-send-email-penguin-ker...@i-love.sakura.ne.jp >> Signed-off-by: Tetsuo Handa <[email protected]> >> Acked-by: Dmitry Vyukov <[email protected]> > > Peter, ping. > Please at least provide some feedback. > This is still the top crasher on syzbot and harms testing of the whole > kernel. I am periodically thinking of disabling LOCKDEP on syzbot as > harming more than helping, but so far talking myself out of it because > it will likely be broken more when we try to re-enable it and I still > hope for a timely resolution of this issue. >
