From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, dsahern@kernel.org, joannelkoong@gmail.com,
kuni1840@gmail.com, netdev@vger.kernel.org,
syzbot+12c506c1aae251e70449@syzkaller.appspotmail.com
Subject: Re: [PATCH v1 net] tcp: Fix refcnt handling in __inet_hash_connect().
Date: Thu, 14 Mar 2024 10:30:29 +0000 [thread overview]
Message-ID: <171041222930.21784.1498217095730507058.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240308201623.65448-1-kuniyu@amazon.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 8 Mar 2024 12:16:23 -0800 you wrote:
> syzbot reported a warning in sk_nulls_del_node_init_rcu().
>
> The commit 66b60b0c8c4a ("dccp/tcp: Unhash sk from ehash for tb2 alloc
> failure after check_estalblished().") tried to fix an issue that an
> unconnected socket occupies an ehash entry when bhash2 allocation fails.
>
> In such a case, we need to revert changes done by check_established(),
> which does not hold refcnt when inserting socket into ehash.
>
> [...]
Here is the summary with links:
- [v1,net] tcp: Fix refcnt handling in __inet_hash_connect().
https://git.kernel.org/netdev/net/c/04d9d1fc428a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-03-14 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 20:16 [PATCH v1 net] tcp: Fix refcnt handling in __inet_hash_connect() Kuniyuki Iwashima
2024-03-14 8:27 ` Eric Dumazet
2024-03-14 10:30 ` 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=171041222930.21784.1498217095730507058.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=joannelkoong@gmail.com \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+12c506c1aae251e70449@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).