linux-kernel - Re: [PATCH 4.19 21/57] proc: dont allow async path resolution of /proc/self components

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]

Message-ID: <395dd137-70d5-e915-92b5-b2a18f44badc@kernel.dk>
Date:   Tue, 2 Mar 2021 10:39:08 -0700
From:   Jens Axboe <axboe@...nel.dk>
To:     Yang Yingliang <yangyingliang@...wei.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org
Cc:     stable@...r.kernel.org, Sasha Levin <sashal@...nel.org>,
        yangerkun <yangerkun@...wei.com>,
        Cheng Jian <cj.chengjian@...wei.com>
Subject: Re: [PATCH 4.19 21/57] proc: dont allow async path resolution of
 /proc/self components

On 3/2/21 1:40 AM, Yang Yingliang wrote:
> Hi,
> 
> On 2020/12/1 16:53, Greg Kroah-Hartman wrote:
>> From: Jens Axboe <axboe@...nel.dk>
>>
>> [ Upstream commit 8d4c3e76e3be11a64df95ddee52e99092d42fc19 ]
>>
>> If this is attempted by a kthread, then return -EOPNOTSUPP as we don't
>> currently support that. Once we can get task_pid_ptr() doing the right
>> thing, then this can go away again.
> 
> https://www.spinics.net/lists/io-uring/msg05297.html
> 
> This patch seems used for io-wq worker which is merged in
> 
> v5.5-rc1, why we need this in linux-4.19.y ?

While that's true, it's also a sane safeguard in general.

-- 
Jens Axboe