From: patchwork-bot+netdevbpf@kernel.org
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: netdev@vger.kernel.org, pabeni@redhat.com,
jiayuan.chen@shopee.com,
syzbot+52624bdfbf2746d37d70@syzkaller.appspotmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
horms@kernel.org, mhal@rbox.co, sven@stegemann.de,
brauner@kernel.org, tom@herbertland.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] kcm: fix zero-frag skb in frag_list on partial sendmsg error
Date: Tue, 24 Feb 2026 01:40:06 +0000 [thread overview]
Message-ID: <177189720655.3267776.15644480509683053572.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260219014256.370092-1-jiayuan.chen@linux.dev>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 19 Feb 2026 09:42:51 +0800 you wrote:
> From: Jiayuan Chen <jiayuan.chen@shopee.com>
>
> Syzkaller reported a warning in kcm_write_msgs() when processing a
> message with a zero-fragment skb in the frag_list.
>
> When kcm_sendmsg() fills MAX_SKB_FRAGS fragments in the current skb,
> it allocates a new skb (tskb) and links it into the frag_list before
> copying data. If the copy subsequently fails (e.g. -EFAULT from
> user memory), tskb remains in the frag_list with zero fragments:
>
> [...]
Here is the summary with links:
- [net,v2] kcm: fix zero-frag skb in frag_list on partial sendmsg error
https://git.kernel.org/netdev/net/c/ca220141fa8e
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-02-24 1:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 1:42 [PATCH net v2] kcm: fix zero-frag skb in frag_list on partial sendmsg error Jiayuan Chen
2026-02-24 1:40 ` 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=177189720655.3267776.15644480509683053572.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiayuan.chen@linux.dev \
--cc=jiayuan.chen@shopee.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhal@rbox.co \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sven@stegemann.de \
--cc=syzbot+52624bdfbf2746d37d70@syzkaller.appspotmail.com \
--cc=tom@herbertland.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