Re: [PATCH net-next v3] af_unix: pass pidfd flags via SCM_PIDFD cmsg

2024-11-22 Thread Christian Brauner
On Thu, Nov 21, 2024 at 01:57:32PM +0100, Alexander Mikhalitsyn wrote: > >Currently SCM_PIDFD cmsg cannot be sent via unix socket > >(returns -EINVAL) and SO_PASSPIDFD doesn't support flags. > >The created pidfd always has flags set to 0. > > > >This patch implements SCM_PIDFD cmsg in AF_UNIX socke

Re: [PATCH net-next v3] af_unix: pass pidfd flags via SCM_PIDFD cmsg

2024-11-21 Thread stsp
21.11.2024 15:57, Alexander Mikhalitsyn пишет: Hi Stas! Hmm, it is a bit unusual that SCM_PIDFD message format is different in case when you send it and when you read it. I mean that when you read it (on the receiver side) you get pidfd file descriptor number, while when you write it (on the s

Re: [PATCH net-next v3] af_unix: pass pidfd flags via SCM_PIDFD cmsg

2024-11-21 Thread Alexander Mikhalitsyn
>Currently SCM_PIDFD cmsg cannot be sent via unix socket >(returns -EINVAL) and SO_PASSPIDFD doesn't support flags. >The created pidfd always has flags set to 0. > >This patch implements SCM_PIDFD cmsg in AF_UNIX socket, which >can be used to send flags to SO_PASSPIDFD-enabled recipient. > >Self-te

Re: [PATCH net-next v3] af_unix: pass pidfd flags via SCM_PIDFD cmsg

2024-11-19 Thread stsp
18.11.2024 20:54, Kuniyuki Iwashima пишет: From: Stas Sergeev Date: Sat, 16 Nov 2024 13:11:20 +0300 Currently SCM_PIDFD cmsg cannot be sent via unix socket (returns -EINVAL) and SO_PASSPIDFD doesn't support flags. The created pidfd always has flags set to 0. This patch implements SCM_PIDFD cms

Re: [PATCH net-next v3] af_unix: pass pidfd flags via SCM_PIDFD cmsg

2024-11-18 Thread Kuniyuki Iwashima
From: Stas Sergeev Date: Sat, 16 Nov 2024 13:11:20 +0300 > Currently SCM_PIDFD cmsg cannot be sent via unix socket > (returns -EINVAL) and SO_PASSPIDFD doesn't support flags. > The created pidfd always has flags set to 0. > > This patch implements SCM_PIDFD cmsg in AF_UNIX socket, which > can be