From: Hillf Danton <hdanton@sina.com>
To: Eric Dumazet <edumazet@google.com>
Cc: syzbot <syzbot+05f9cecd28e356241aba@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Boqun Feng <boqun.feng@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] INFO: task hung in new_device_store (5)
Date: Sat, 28 Sep 2024 08:06:57 +0800 [thread overview]
Message-ID: <20240928000657.1247-1-hdanton@sina.com> (raw)
In-Reply-To: <CANn89iJMHqg4e_tErTERx=-ERXbA+CRbeC0chp9ofqANwwjhLA@mail.gmail.com>
On Fri, 27 Sep 2024 13:54:59 +0200 Eric Dumazet <edumazet@google.com>
> On Fri, Sep 27, 2024 at 1:44 PM Hillf Danton <hdanton@sina.com> wrote:
> >
> > On Fri, 27 Sep 2024 13:24:54 +0200 Eric Dumazet <edumazet@google.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.
>
Is this the typical dude style in Paris when showing deadlock?
> lockdep is usually right. And here there is an actua syzbot report.
The word maintainer is abused in this case.
next prev parent reply other threads:[~2024-09-28 0:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 17:58 syzbot
2024-09-26 20:14 ` Eric Dumazet
2024-09-27 11:04 ` Hillf Danton
2024-09-27 11:24 ` Eric Dumazet
2024-09-27 11:27 ` Eric Dumazet
2024-09-27 11:41 ` Hillf Danton
2024-09-27 11:54 ` Eric Dumazet
2024-09-28 0:06 ` Hillf Danton [this message]
2024-10-09 8:20 ` syzbot
2025-12-25 16:24 ` syzbot
2025-12-29 6:36 ` Tetsuo Handa
2025-12-29 7:02 ` syzbot
2025-12-29 9:36 ` Tetsuo Handa
2025-12-29 12:22 ` syzbot
2025-12-29 14:18 ` Tetsuo Handa
2025-12-29 15:10 ` syzbot
2025-12-30 1:29 ` Tetsuo Handa
2025-12-30 2:08 ` syzbot
2025-12-30 3:07 ` Tetsuo Handa
2025-12-30 3:33 ` syzbot
2025-12-30 9:11 ` Hillf Danton
2025-12-30 9:38 ` syzbot
2025-12-30 13:24 ` Tetsuo Handa
2025-12-30 14:18 ` syzbot
2026-01-02 10:18 ` Tetsuo Handa
2026-01-02 10:53 ` syzbot
2026-01-03 9:59 ` Tetsuo Handa
2026-01-03 11:24 ` syzbot
2026-01-03 14:07 ` Tetsuo Handa
2026-01-03 14:33 ` syzbot
2025-12-30 7:48 ` Tetsuo Handa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240928000657.1247-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=boqun.feng@gmail.com \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=syzbot+05f9cecd28e356241aba@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®