All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Arjun Roy <arjunroy.kdev@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, arjunroy@google.com,
	edumazet@google.com, soheil@google.com, kuba@kernel.org
Subject: Re: [net v3] tcp: Specify cmsgbuf is user pointer for receive zerocopy.
Date: Fri, 07 May 2021 01:10:09 +0000	[thread overview]
Message-ID: <162034980934.23850.4657728582811464794.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210506223530.2266456-1-arjunroy.kdev@gmail.com>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Thu,  6 May 2021 15:35:30 -0700 you wrote:
> From: Arjun Roy <arjunroy@google.com>
> 
> A prior change (1f466e1f15cf) introduces separate handling for
> ->msg_control depending on whether the pointer is a kernel or user
> pointer. However, while tcp receive zerocopy is using this field, it
> is not properly annotating that the buffer in this case is a user
> pointer. This can cause faults when the improper mechanism is used
> within put_cmsg().
> 
> [...]

Here is the summary with links:
  - [net,v3] tcp: Specify cmsgbuf is user pointer for receive zerocopy.
    https://git.kernel.org/netdev/net/c/a6f8ee58a8e3

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



      reply	other threads:[~2021-05-07  1:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06 22:35 [net v3] tcp: Specify cmsgbuf is user pointer for receive zerocopy Arjun Roy
2021-05-07  1: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=162034980934.23850.4657728582811464794.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=arjunroy.kdev@gmail.com \
    --cc=arjunroy@google.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=soheil@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.