Re: BUG: MAX_LOCKDEP_CHAINS too low!

[Cong Wang]

On Wed, Mar 4, 2020 at 12:03 AM Dmitry Vyukov <dvyukov@xxxxxxxxxx> wrote:
>
> On Sat, Jan 18, 2020 at 9:41 PM Cong Wang <xiyou.wangcong@xxxxxxxxx> wrote:
> >
> > On Thu, Jan 16, 2020 at 7:09 AM Taehee Yoo <ap420073@xxxxxxxxx> wrote:
> > > Yes, I fully agree with this.
> > > If we calculate the subclass for lock_nested() very well, I think we
> > > might use static lockdep key for addr_list_lock_key too. I think
> > > "dev->upper_level" and "dev->lower_level" might be used as subclass.
> > > These values are updated recursively in master/nomaster operation.
> >
> > Great! I will think about this too. At least I will remove the other keys
> > for net-next.
>
> Hi Cong,
>
> Was this done? This still harms testing of the whole kernel. Disabling
> LOCKDEP does not look good either...

Not yet, I have a half-done patch locally, will work on it to make it
complete for net-next.

Thanks for reminding me!