[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89iJMHqg4e_tErTERx=-ERXbA+CRbeC0chp9ofqANwwjhLA@mail.gmail.com>
Date: Fri, 27 Sep 2024 13:54:59 +0200
From: Eric Dumazet <edumazet@...gle.com>
To: Hillf Danton <hdanton@...a.com>
Cc: syzbot <syzbot+05f9cecd28e356241aba@...kaller.appspotmail.com>,
linux-kernel@...r.kernel.org,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>, Boqun Feng <boqun.feng@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>, netdev@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [net?] INFO: task hung in new_device_store (5)
On Fri, Sep 27, 2024 at 1:44 PM Hillf Danton <hdanton@...a.com> wrote:
>
> On Fri, 27 Sep 2024 13:24:54 +0200 Eric Dumazet <edumazet@...gle.com>
> > I suggest you look at why we have to use rtnl_trylock()
> >
> > If you know better, please send patches to remove all instances.
>
> No patch is needed before you show us deadlock. I suspect you could
> spot a case where lockdep fails to report deadlock.
Please try to not educate maintainers about their stuff.
lockdep is usually right. And here there is an actua syzbot report.
Powered by blists - more mailing lists