Re: [PATCH] lockdep: Introduce CONFIG_LOCKDEP_LARGE

2020-08-18 Thread Tetsuo Handa
Peter, Ingo and Will. Would you answer (Q1) and (Q2)? On 2020/08/18 21:02, Dmitry Vyukov wrote: > On Tue, Aug 18, 2020 at 1:07 PM Tetsuo Handa > wrote: >> >> On 2020/08/18 18:57, Dmitry Vyukov wrote: >>> On Tue, Aug 4, 2020 at 4:36 AM Tetsuo Handa >>> wrote: Hello, Peter, Ingo and

Re: [PATCH] lockdep: Introduce CONFIG_LOCKDEP_LARGE

2020-08-18 Thread Dmitry Vyukov
On Tue, Aug 18, 2020 at 1:07 PM Tetsuo Handa wrote: > > On 2020/08/18 18:57, Dmitry Vyukov wrote: > > On Tue, Aug 4, 2020 at 4:36 AM Tetsuo Handa > > wrote: > >> > >> Hello, Peter, Ingo and Will. > >> > >> (Q1) Can we change the capacity using kernel config? > >> > >> (Q2) If we can change the

Re: [PATCH] lockdep: Introduce CONFIG_LOCKDEP_LARGE

2020-08-18 Thread Tetsuo Handa
On 2020/08/18 18:57, Dmitry Vyukov wrote: > On Tue, Aug 4, 2020 at 4:36 AM Tetsuo Handa > wrote: >> >> Hello, Peter, Ingo and Will. >> >> (Q1) Can we change the capacity using kernel config? >> >> (Q2) If we can change the capacity, is it OK to specify these constants >> independently? (In

Re: [PATCH] lockdep: Introduce CONFIG_LOCKDEP_LARGE

2020-08-18 Thread Dmitry Vyukov
On Tue, Aug 4, 2020 at 4:36 AM Tetsuo Handa wrote: > > Hello, Peter, Ingo and Will. > > (Q1) Can we change the capacity using kernel config? > > (Q2) If we can change the capacity, is it OK to specify these constants > independently? (In other words, is there inter-dependency among >

Re: [PATCH] lockdep: Introduce CONFIG_LOCKDEP_LARGE

2020-08-03 Thread Tetsuo Handa
Hello, Peter, Ingo and Will. (Q1) Can we change the capacity using kernel config? (Q2) If we can change the capacity, is it OK to specify these constants independently? (In other words, is there inter-dependency among these constants?) (Q3) Do you think that we can extend lockdep to

Re: [PATCH] lockdep: Introduce CONFIG_LOCKDEP_LARGE

2020-07-24 Thread Tetsuo Handa
On 2020/07/25 13:48, Dmitry Vyukov wrote: >> diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c >> index 29a8de4..85ba7eb 100644 >> --- a/kernel/locking/lockdep.c >> +++ b/kernel/locking/lockdep.c >> @@ -1349,7 +1349,11 @@ static int add_lock_to_list(struct lock_class *this, >> /*

Re: [PATCH] lockdep: Introduce CONFIG_LOCKDEP_LARGE

2020-07-24 Thread Dmitry Vyukov
On Sat, Jul 25, 2020 at 3:30 AM Tetsuo Handa 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

[PATCH] lockdep: Introduce CONFIG_LOCKDEP_LARGE

2020-07-24 Thread Tetsuo Handa
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]. Like