[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190417140106.GG32622@redhat.com>
Date: Wed, 17 Apr 2019 16:01:06 +0200
From: Oleg Nesterov <oleg@...hat.com>
To: Christian Brauner <christian@...uner.io>
Cc: torvalds@...ux-foundation.org, viro@...iv.linux.org.uk,
jannh@...gle.com, dhowells@...hat.com, linux-api@...r.kernel.org,
linux-kernel@...r.kernel.org, serge@...lyn.com, luto@...nel.org,
arnd@...db.de, ebiederm@...ssion.com, keescook@...omium.org,
tglx@...utronix.de, mtk.manpages@...il.com,
akpm@...ux-foundation.org, cyphar@...har.com,
joel@...lfernandes.org, dancol@...gle.com
Subject: Re: [PATCH v1 3/4] signal: support CLONE_PIDFD with pidfd_send_signal
On 04/16, Christian Brauner wrote:
>
> @@ -3581,12 +3588,12 @@ SYSCALL_DEFINE4(pidfd_send_signal, int, pidfd, int, sig,
> if (flags)
> return -EINVAL;
>
> - f = fdget_raw(pidfd);
> + f = fdget(pidfd);
could you explain this change?
I am just curious, I don't understand why should we disallow O_PATH and how
this connects to this patch.
Oleg.
Powered by blists - more mailing lists