[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230805-ignorant-kahlkopf-9749ac3cd20a@brauner>
Date: Sat, 5 Aug 2023 19:17:54 +0200
From: Christian Brauner <brauner@...nel.org>
To: Aleksa Sarai <cyphar@...har.com>
Cc: Christian Brauner <brauner@...nel.org>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org, Alexander Viro <viro@...iv.linux.org.uk>,
Jens Axboe <axboe@...nel.dk>
Subject: Re: [PATCH] open: make RESOLVE_CACHED correctly test for O_TMPFILE
On Sun, 06 Aug 2023 02:11:58 +1000, Aleksa Sarai wrote:
> O_TMPFILE is actually __O_TMPFILE|O_DIRECTORY. This means that the old
> fast-path check for RESOLVE_CACHED would reject all users passing
> O_DIRECTORY with -EAGAIN, when in fact the intended test was to check
> for __O_TMPFILE.
>
>
Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.fixes
[1/1] open: make RESOLVE_CACHED correctly test for O_TMPFILE
https://git.kernel.org/vfs/vfs/c/7c62794bc37f
Powered by blists - more mailing lists