The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jann Horn <jannh@google.com>
Cc: edumazet@google.com, kuniyu@google.com, pabeni@redhat.com,
	willemb@google.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, john.fastabend@gmail.com
Subject: Re: [PATCH] net: block MSG_NO_SHARED_FRAGS in sendmsg()
Date: Fri, 15 May 2026 01:20:21 +0000	[thread overview]
Message-ID: <177880802129.150313.8491869548360910151.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260512-msg_no_shared_frags-v1-1-55ea46760331@google.com>

Hello:

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

On Tue, 12 May 2026 16:02:03 +0200 you wrote:
> This change should cause no difference in behavior; it just cleans up some
> hazardous code that could have become a problem in the future.
> 
> MSG_NO_SHARED_FRAGS is a kernel-internal flag that cancels the effect of
> MSG_SPLICE_PAGES, another kernel-internal flag that influences the
> data-sharing semantics of SKBs.
> 
> [...]

Here is the summary with links:
  - net: block MSG_NO_SHARED_FRAGS in sendmsg()
    https://git.kernel.org/netdev/net-next/c/4987a5763fd5

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



      parent reply	other threads:[~2026-05-15  1:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12 14:02 [PATCH] net: block MSG_NO_SHARED_FRAGS in sendmsg() Jann Horn
2026-05-13  8:50 ` David Laight
2026-05-13 12:55   ` Jann Horn
2026-05-15  1:20 ` 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=177880802129.150313.8491869548360910151.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=edumazet@google.com \
    --cc=jannh@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox