From: Hillf Danton <hdanton@sina.com>
To: Eric Dumazet <edumazet@google.com>
Cc: "Shin'ichiro Kawasaki" <shinichiro.kawasaki@wdc.com>,
syzbot <syzbot+2d770620059281e225a4@syzkaller.appspotmail.com>,
Nilay Shroff <nilay@linux.ibm.com>,
Keith Busch <kbusch@kernel.org>,
boqun@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, peterz@infradead.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING: locking bug in tcp_tsq_handler
Date: Wed, 26 Aug 2026 18:27:16 +0800 [thread overview]
Message-ID: <20260826102718.1550-1-hdanton@sina.com> (raw)
In-Reply-To: <CANn89iKEVEs5=K1Uhj_CHagbt+eV0QGernwz9EBFkLEZOB1FAw@mail.gmail.com>
On Wed, 26 Aug 2026 06:05:15 +0200 Eric Dumazet wrote:
>On Wed, Aug 26, 2026 at 5:06 AM Hillf Danton <hdanton@sina.com> wrote:
>> On Tue, 25 Aug 2026 22:26:25 +0900 Shin'ichiro Kawasaki wrote:
>> >On Aug 25, 2026 / 14:45, Hillf Danton wrote:
>> >> On Tue, 25 Aug 2026 14:44:35 +0900 Shin'ichiro Kawasaki wrote:
>> >> > On Aug 25, 2026 / 03:50, Eric Dumazet wrote:
>> >> > >
>> >> > > I think 19bdb70c77d3 should be reverted.
>> >> >
>> >> > Just reverting the commit will reintroduce the other lockdep WARN that the
>> >> > commit addressed. I hope to have another fix to avoid the WARN.
>> >> >
>> >> I do not think you know the root cause of that lockdep warn, so reverting
>> >> 19bdb70c77d3 is the right thing to do because of [11, 12].
>> >>
>> >> [11] ffa1e7ada456 ("block: Make request_queue lockdep splats show up earlier")
>> >> [12] Subject: Re: [PATCH] nbd: don't warn when reclassifying a busy socket lock
>> >> https://lore.kernel.org/lkml/20260816014906.1149-1-hdanton@sina.com/
>> >
>> > I took a look in the commit [11] and the discussion [12], but couldn't follow
>> > why the commit 19bdb70c77d3 should be reverted. Could you elaborate a bit more
>> > about the reason you suggest the revert?
>> >
>> The Fixes tag in d532cddb6c60 proves Eric delivered a HBC, half baked croissant,
>> to lore. And the nvme-tcp tucked in the HBC hints Eric copied something from
>> somewhere. Finally the absence of ffa1e7ada456 in 19bdb70c77d3 proves it is
>> worse than a HBC. Clear dude? Or go to read [12] again?
>
> linux development is iterative, we do not submit a single patch fixing
> 1000 bugs at once.
>
The iterative word fails to justify you can submit any fix before understanding
the root cause.
> I decided to ignore your rants a long time ago, as many others did.
>
Your HBC forced you to quiese instead just like the ostrich burying his head
in sand.
> How many bugs did you fix last year?
More than 150 [13].
[13] Subject: Re: some works in 2025
https://lore.kernel.org/lkml/20251112225650.9224-1-hdanton@sina.com/
next prev parent reply other threads:[~2026-08-26 10:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 15:51 [PATCH] locking/lockdep: Invalidate stale class_cache entries for zapped classes Eric Dumazet
2026-08-25 0:29 ` Hillf Danton
2026-08-25 0:59 ` [syzbot] [net?] WARNING: locking bug in tcp_tsq_handler syzbot
2026-08-25 1:25 ` Hillf Danton
2026-08-25 1:27 ` Eric Dumazet
2026-08-25 1:50 ` Eric Dumazet
2026-08-25 5:44 ` Shin'ichiro Kawasaki
2026-08-25 6:25 ` Hillf Danton
2026-08-25 6:45 ` Hillf Danton
2026-08-25 13:26 ` Shin'ichiro Kawasaki
2026-08-25 13:53 ` Eric Dumazet
2026-08-25 14:27 ` Eric Dumazet
2026-08-26 2:23 ` Shin'ichiro Kawasaki
2026-08-27 12:31 ` Hillf Danton
2026-08-26 3:06 ` Hillf Danton
2026-08-26 4:05 ` Eric Dumazet
2026-08-26 10:27 ` Hillf Danton [this message]
2026-08-26 10:49 ` Eric Dumazet
2026-08-26 11:49 ` Hillf Danton
2026-08-28 9:00 ` Hillf Danton
2026-08-25 13:08 ` Shin'ichiro Kawasaki
-- strict thread matches above, loose matches on Subject: below --
2026-08-24 15:44 syzbot
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=20260826102718.1550-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=boqun@kernel.org \
--cc=edumazet@google.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nilay@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=syzbot+2d770620059281e225a4@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.