Netdev List
 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: Wed, 26 Aug 2026 19:49:20 +0800	[thread overview]
Message-ID: <20260826114921.1572-1-hdanton@sina.com> (raw)
In-Reply-To: <CANn89iKFGKENq+cFHC7p6ekKXpYhpvZQdA1-TAoriFi09tPqrg@mail.gmail.com>

On Wed, 26 Aug 2026 12:49:36 +0200 Eric Dumazet wrote:
> On Wed, Aug 26, 2026 at 12:27 PM Hillf Danton <hdanton@sina.com> wrote:
> > On Wed, 26 Aug 2026 06:05:15 +0200 Eric Dumazet wrote:
> > > How many bugs did you fix last year?
> >
> > More than 150 [13].
> 
> Pure hallucination.
> 
> $ git log --author "Hillf Danton" --oneline --since 1year | wc -l
> 0
> 
Before it is proved that linux can make the earth a better place for
everyone, who cares LPC/Unix for example?

> Lets compare to some real numbers.
> 
> $ git log --author "Eric Dumazet" --oneline --since 1year | wc -l
> 550
> 
HBC in addition to nobrain can also land upstream, no?
How many reverts landed upstream in 2025?

> Harassing a maintainer is probably not a good thing, I wish you luck.

The Harassing word in combination with HBC puts shame on the maintainer's face.

  reply	other threads:[~2026-08-26 11:50 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 [this message]
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=20260826114921.1572-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox