netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: john.fastabend@gmail.com, jakub@cloudflare.com, ast@kernel.org,
	daniel@iogearbox.net, kuni1840@gmail.com, netdev@vger.kernel.org,
	bpf@vger.kernel.org,
	syzbot+4cabd1d2fa917a456db8@syzkaller.appspotmail.com
Subject: Re: [PATCH v1 bpf] tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock->cork.
Date: Wed, 10 Sep 2025 14:10:05 +0000	[thread overview]
Message-ID: <175751340576.1437658.9381331742790969125.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250909232623.4151337-1-kuniyu@google.com>

Hello:

This patch was applied to bpf/bpf.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:

On Tue,  9 Sep 2025 23:26:12 +0000 you wrote:
> syzbot reported the splat below. [0]
> 
> The repro does the following:
> 
>   1. Load a sk_msg prog that calls bpf_msg_cork_bytes(msg, cork_bytes)
>   2. Attach the prog to a SOCKMAP
>   3. Add a socket to the SOCKMAP
>   4. Activate fault injection
>   5. Send data less than cork_bytes
> 
> [...]

Here is the summary with links:
  - [v1,bpf] tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock->cork.
    https://git.kernel.org/bpf/bpf/c/a3967baad4d5

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



      parent reply	other threads:[~2025-09-10 14:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09 23:26 [PATCH v1 bpf] tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock->cork Kuniyuki Iwashima
2025-09-10  5:15 ` Martin KaFai Lau
2025-09-10  6:56   ` Kuniyuki Iwashima
2025-09-10 14:05     ` Martin KaFai Lau
2025-09-10 15:59       ` Kuniyuki Iwashima
2025-09-10 14:10 ` 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=175751340576.1437658.9381331742790969125.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=jakub@cloudflare.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuni1840@gmail.com \
    --cc=kuniyu@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=syzbot+4cabd1d2fa917a456db8@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).