linux-kernel - Re: [PATCH] io_uring/fs: consider link->flags when getting path for LINKAT

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: <b7a7627a-da93-47e7-b26d-08f918de10ea@kernel.dk>
Date:   Mon, 20 Nov 2023 09:38:56 -0700
From:   Jens Axboe <axboe@...nel.dk>
To:     Charles Mirabile <cmirabil@...hat.com>
Cc:     linux-kernel@...r.kernel.org, asml.silence@...il.com,
        io-uring@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] io_uring/fs: consider link->flags when getting path for
 LINKAT

On 11/20/23 9:34 AM, Charles Mirabile wrote:
> On Mon, Nov 20, 2023 at 10:59 AM Jens Axboe <axboe@...nel.dk> wrote:
>>
>> On 11/20/23 3:55 AM, Charles Mirabile wrote:
>>> In order for `AT_EMPTY_PATH` to work as expected, the fact
>>> that the user wants that behavior needs to make it to `getname_flags`
>>> or it will return ENOENT.
>>
>> Looks good - do you have a liburing test case for this too?
> Yes, see here https://github.com/axboe/liburing/issues/995 and here
> https://github.com/axboe/liburing/pull/996.

Ah thank you - for some reason github stopped notifying me...

-- 
Jens Axboe