All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 28 Aug 2026 17:00:56 +0800	[thread overview]
Message-ID: <20260828090059.1895-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:
> 
> I decided to ignore your rants a long time ago, as many others did.
> 
Aha another rant chance for showing you the steps to quiese syzbot that
reported deadlock.

[11] Subject: Re: [syzbot] [input?] possible deadlock in tasklet_action_common (2)
https://lore.kernel.org/lkml/6a913c08.4d659fcc.734b4.001b.GAE@google.com/

[12] Subject: Re: [syzbot] [input?] possible deadlock in tasklet_action_common (2)
https://lore.kernel.org/lkml/6a90ef26.27659fcc.2ceef7.0018.GAE@google.com/

This is one of my good works in 2026 in addition to catch your HBCs.

  parent reply	other threads:[~2026-08-28  9:01 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
2026-08-26 10:49                     ` Eric Dumazet
2026-08-26 11:49                       ` Hillf Danton
2026-08-28  9:00                   ` Hillf Danton [this message]
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=20260828090059.1895-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.