netdev - Re: [PATCH] net/unix: use consistent error code in SO

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Tue, 08 Aug 2023 23:40:24 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: David Rheinsberg <david@...dahead.eu>
Cc: netdev@...r.kernel.org, alexander@...alicyn.com, brauner@...nel.org,
 davem@...emloft.net, sdf@...gle.com, bluca@...ian.org, edumazet@...gle.com
Subject: Re: [PATCH] net/unix: use consistent error code in SO_PEERPIDFD

Hello:

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

On Mon,  7 Aug 2023 10:12:25 +0200 you wrote:
> Change the new (unreleased) SO_PEERPIDFD sockopt to return ENODATA
> rather than ESRCH if a socket type does not support remote peer-PID
> queries.
> 
> Currently, SO_PEERPIDFD returns ESRCH when the socket in question is
> not an AF_UNIX socket. This is quite unexpected, given that one would
> assume ESRCH means the peer process already exited and thus cannot be
> found. However, in that case the sockopt actually returns EINVAL (via
> pidfd_prepare()). This is rather inconsistent with other syscalls, which
> usually return ESRCH if a given PID refers to a non-existant process.
> 
> [...]

Here is the summary with links:
  - net/unix: use consistent error code in SO_PEERPIDFD
    https://git.kernel.org/netdev/net/c/b6f79e826fbd

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