[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<173317563075.3902418.2961842712438149169.git-patchwork-notify@kernel.org>
Date: Mon, 02 Dec 2024 21:40:30 +0000
From: patchwork-bot+bluetooth@...nel.org
To: Michal Luczaj <mhal@...x.co>
Cc: marcel@...tmann.org, johan.hedberg@...il.com, luiz.dentz@...il.com,
davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
horms@...nel.org, dhowells@...hat.com, marc.dionne@...istor.com,
luiz.von.dentz@...el.com, linux-bluetooth@...r.kernel.org,
netdev@...r.kernel.org, linux-afs@...ts.infradead.org, kuba@...nel.org,
dw@...idwei.uk
Subject: Re: [PATCH net v3 0/4] net: Fix some callers of copy_from_sockptr()
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@...el.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
https://git.kernel.org/bluetooth/bluetooth-next/c/389eeaf59809
- [net,v3,2/4] llc: Improve setsockopt() handling of malformed user input
(no matching commit)
- [net,v3,3/4] rxrpc: Improve setsockopt() handling of malformed user input
(no matching commit)
- [net,v3,4/4] net: Comment copy_from_sockptr() explaining its behaviour
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists