Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: edumazet@google.com, ncardwell@google.com, davem@davemloft.net,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	bigeasy@linutronix.de, clrkwllms@kernel.org, rostedt@goodmis.org,
	tglx@kernel.org, kuni1840@gmail.com, netdev@vger.kernel.org,
	syzbot+e809069bc15f26300526@syzkaller.appspotmail.com
Subject: Re: [PATCH v2 net] tcp: Add preempt_{disable,enable}_nested() in reqsk_queue_hash_req().
Date: Tue, 02 Jun 2026 19:00:07 +0000	[thread overview]
Message-ID: <178042680740.1007375.14491547621037565757.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260601182101.3183993-1-kuniyu@google.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon,  1 Jun 2026 18:20:55 +0000 you wrote:
> syzbot reported a weird reqsk->rsk_refcnt underflow in
> __inet_csk_reqsk_queue_drop().
> 
> The captured reqsk_put() in __inet_csk_reqsk_queue_drop()
> is called only when it successfully removes reqsk from ehash.
> 
> Moreover, reqsk_timer_handler() calls another reqsk_put()
> after that.
> 
> [...]

Here is the summary with links:
  - [v2,net] tcp: Add preempt_{disable,enable}_nested() in reqsk_queue_hash_req().
    https://git.kernel.org/netdev/net/c/e10902df2448

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-06-02 19:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01 18:20 [PATCH v2 net] tcp: Add preempt_{disable,enable}_nested() in reqsk_queue_hash_req() Kuniyuki Iwashima
2026-06-01 18:46 ` Eric Dumazet
2026-06-02  6:25 ` Sebastian Andrzej Siewior
2026-06-02 19:00 ` patchwork-bot+netdevbpf [this message]

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=178042680740.1007375.14491547621037565757.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=clrkwllms@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuni1840@gmail.com \
    --cc=kuniyu@google.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=syzbot+e809069bc15f26300526@syzkaller.appspotmail.com \
    --cc=tglx@kernel.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