From: patchwork-bot+netdevbpf@kernel.org
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
willemb@google.com, kees@kernel.org, jlayton@kernel.org,
runyu.xiao@seu.edu.cn, leitao@debian.org, gustavoars@kernel.org,
joe@dama.to, sdf@fomichev.me, lirongqing@baidu.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: raw: fix ICMP unreachable sent when receive queue is full
Date: Tue, 10 Nov 2026 02:54:36 +0000 [thread overview]
Message-ID: <179427927617.3612825.16017397193883972723.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261104115732.322151-1-jiayuan.chen@linux.dev>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 4 Nov 2026 19:57:26 +0800 you wrote:
> It's found in a raw socket application. When the application doesn't
> read packets in time, the client receives ICMP Protocol Unreachable,
> which makes the client abort the session.
>
> The reason is that the server hits the sk_rcvbuf limit, and
> raw_v4_input() skips the socket before setting 'delivered', so it
> returns 0. Then ip_protocol_deliver_rcu() sees 'raw' is 0, thinks no one
> handles this protocol and calls icmp_send() to send ICMP Protocol
> Unreachable.
>
> [...]
Here is the summary with links:
- [net] net: raw: fix ICMP unreachable sent when receive queue is full
https://git.kernel.org/netdev/net/c/45441a94d502
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:[~2026-11-10 2:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 11:57 Jiayuan Chen
2026-11-10 2:54 ` 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=179427927617.3612825.16017397193883972723.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=gustavoars@kernel.org \
--cc=horms@kernel.org \
--cc=jiayuan.chen@linux.dev \
--cc=jlayton@kernel.org \
--cc=joe@dama.to \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=runyu.xiao@seu.edu.cn \
--cc=sdf@fomichev.me \
--cc=willemb@google.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
all inboxes | Powered by JetHome®