All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
	edumazet@google.com, syzkaller@googlegroups.com,
	talalahmad@google.com, arjunroy@google.com, willemb@google.com,
	soheil@google.com
Subject: Re: [PATCH net] tcp: take care of mixed splice()/sendmsg(MSG_ZEROCOPY) case
Date: Sat, 05 Feb 2022 04:30:09 +0000	[thread overview]
Message-ID: <164403540926.14792.15149477966460152526.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220203225547.665114-1-eric.dumazet@gmail.com>

Hello:

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

On Thu,  3 Feb 2022 14:55:47 -0800 you wrote:
> From: Eric Dumazet <edumazet@google.com>
> 
> syzbot found that mixing sendpage() and sendmsg(MSG_ZEROCOPY)
> calls over the same TCP socket would again trigger the
> infamous warning in inet_sock_destruct()
> 
> 	WARN_ON(sk_forward_alloc_get(sk));
> 
> [...]

Here is the summary with links:
  - [net] tcp: take care of mixed splice()/sendmsg(MSG_ZEROCOPY) case
    https://git.kernel.org/netdev/net/c/f8d9d938514f

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



      parent reply	other threads:[~2022-02-05  4:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 22:55 [PATCH net] tcp: take care of mixed splice()/sendmsg(MSG_ZEROCOPY) case Eric Dumazet
2022-02-04 14:39 ` Soheil Hassas Yeganeh
2022-02-05  4:06 ` Jakub Kicinski
2022-02-05  4:20   ` Eric Dumazet
2022-02-05  4: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=164403540926.14792.15149477966460152526.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=arjunroy@google.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=soheil@google.com \
    --cc=syzkaller@googlegroups.com \
    --cc=talalahmad@google.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.