[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <935b000c-77df-fa88-6e2e-daffc256a11e@schaufler-ca.com>
Date: Fri, 26 Mar 2021 09:03:31 -0700
From: Casey Schaufler <casey@...aufler-ca.com>
To: Jens Axboe <axboe@...nel.dk>,
Kentaro Takeda <takedakn@...data.co.jp>,
Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
Cc: linux-security-module@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] tomoyo: don't special case PF_IO_WORKER for PF_KTHREAD
On 3/25/2021 5:44 PM, Jens Axboe wrote:
> The io_uring PF_IO_WORKER threads no longer have PF_KTHREAD set, so no
> need to special case them for credential checks.
Could you cite the commit where that change was made?
>
> Cc: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
> Signed-off-by: Jens Axboe <axboe@...nel.dk>
> ---
> security/tomoyo/network.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/security/tomoyo/network.c b/security/tomoyo/network.c
> index 478f757ff843..8dc61335f65e 100644
> --- a/security/tomoyo/network.c
> +++ b/security/tomoyo/network.c
> @@ -613,7 +613,7 @@ static int tomoyo_check_unix_address(struct sockaddr *addr,
> static bool tomoyo_kernel_service(void)
> {
> /* Nothing to do if I am a kernel service. */
> - return (current->flags & (PF_KTHREAD | PF_IO_WORKER)) == PF_KTHREAD;
> + return current->flags & PF_KTHREAD;
> }
>
> /**
Powered by blists - more mailing lists