All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Michal Luczaj <mhal@rbox.co>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
	luiz.dentz@gmail.com, davem@davemloft.net, edumazet@google.com,
	pabeni@redhat.com, horms@kernel.org, dhowells@redhat.com,
	marc.dionne@auristor.com, luiz.von.dentz@intel.com,
	linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
	linux-afs@lists.infradead.org, kuba@kernel.org, dw@davidwei.uk
Subject: Re: [PATCH net v3 0/4] net: Fix some callers of copy_from_sockptr()
Date: Thu, 28 Nov 2024 08:30:37 +0000	[thread overview]
Message-ID: <173278263749.1659134.13660124936844391608.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241119-sockptr-copy-fixes-v3-0-d752cac4be8e@rbox.co>

Hello:

This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Tue, 19 Nov 2024 14:31:39 +0100 you wrote:
> Some callers misinterpret copy_from_sockptr()'s return value. The function
> follows copy_from_user(), i.e. returns 0 for success, or the number of
> bytes not copied on error. Simply returning the result in a non-zero case
> isn't usually what was intended.
> 
> Compile tested with CONFIG_LLC, CONFIG_AF_RXRPC, CONFIG_BT enabled.
> 
> [...]

Here is the summary with links:
  - [net,v3,1/4] Bluetooth: Improve setsockopt() handling of malformed user input
    (no matching commit)
  - [net,v3,2/4] llc: Improve setsockopt() handling of malformed user input
    https://git.kernel.org/netdev/net/c/1465036b10be
  - [net,v3,3/4] rxrpc: Improve setsockopt() handling of malformed user input
    https://git.kernel.org/netdev/net/c/020200566470
  - [net,v3,4/4] net: Comment copy_from_sockptr() explaining its behaviour
    https://git.kernel.org/netdev/net/c/49b2b973325a

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



  parent reply	other threads:[~2024-11-28  8:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-19 13:31 [PATCH net v3 0/4] net: Fix some callers of copy_from_sockptr() Michal Luczaj
2024-11-19 13:31 ` [PATCH net v3 1/4] Bluetooth: Improve setsockopt() handling of malformed user input Michal Luczaj
2024-11-19 13:51   ` net: Fix some callers of copy_from_sockptr() bluez.test.bot
2024-11-19 13:31 ` [PATCH net v3 2/4] llc: Improve setsockopt() handling of malformed user input Michal Luczaj
2024-11-19 13:31 ` [PATCH net v3 3/4] rxrpc: " Michal Luczaj
2024-11-29 17:04   ` David Howells
2024-11-19 13:31 ` [PATCH net v3 4/4] net: Comment copy_from_sockptr() explaining its behaviour Michal Luczaj
2024-11-26  9:00 ` [PATCH net v3 0/4] net: Fix some callers of copy_from_sockptr() Paolo Abeni
2024-11-26 14:57   ` Luiz Augusto von Dentz
2024-11-28  8:30 ` patchwork-bot+netdevbpf [this message]
2024-12-02 21:40 ` patchwork-bot+bluetooth

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=173278263749.1659134.13660124936844391608.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=dw@davidwei.uk \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=johan.hedberg@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=luiz.von.dentz@intel.com \
    --cc=marc.dionne@auristor.com \
    --cc=marcel@holtmann.org \
    --cc=mhal@rbox.co \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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.