lkml.org 
[lkml]   [2020]   [Nov]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH v3] lockdep: Allow tuning tracing capacity constants.
From
Date
On 2020/11/19 22:06, Dmitry Vyukov wrote:
>>>>
>>>> I am trying to reproduce this locally first. syzbot caims it can
>>>> reproduce it with a number of very simpler reproducers (like spawn
>>>> process, unshare, create socket):
>>>> https://syzkaller.appspot.com/bug?id=8a18efe79140782a88dcd098808d6ab20ed740cc
>>>>
>>>> I see a very slow drift, but it's very slow, so get only to:
>>>> direct dependencies: 22072 [max: 32768]
>>>>
>>>> But that's running a very uniform workload.
>>>>
>>>> However when I tried to cat /proc/lockdep to see if there is anything
>>>> fishy already,
>>>> I got this (on c2e7554e1b85935d962127efa3c2a76483b0b3b6).
>>>>
>>>> Some missing locks?

Not a TOMOYO's bug. Maybe a lockdep's bug.

>
> But I don't know if it's enough to explain the overflow or not...
>

Since you can't hit the limit locally, I guess we need to ask syzbot to
run massive testcases.

\
 
 \ /
  Last update: 2020-11-19 14:47    [W:0.076 / U:2.512 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site