From: Christian Brauner <brauner@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
yukuai3@huawei.com, yangerkun@huaweicloud.com,
Hugh Dickens <hughd@google.com>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH v4 0/5] Improve simple directory offset wrap behavior
Date: Thu, 5 Dec 2024 18:09:14 +0100 [thread overview]
Message-ID: <20241205-jahre-geloben-8f47154d698e@brauner> (raw)
In-Reply-To: <20241204155257.1110338-1-cel@kernel.org>
On Wed, 04 Dec 2024 10:52:51 -0500, cel@kernel.org wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
>
> The purpose of this series is to construct a set of upstream fixes
> that can be backported to v6.6 to address CVE-2024-46701.
>
> My original plan was to add a cursor dentry. However, I've found a
> solution that does not need one. In fact, most or all of the
> reported issues are gone with 4/5. Thus I'm not sure 5/5 is
> necessary, but it seems like a robust improvement.
>
> [...]
Applied to the vfs-6.14.misc branch of the vfs/vfs.git tree.
Patches in the vfs-6.14.misc 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-6.14.misc
[1/5] libfs: Return ENOSPC when the directory offset range is exhausted
https://git.kernel.org/vfs/vfs/c/3569cc5260ac
[2/5] Revert "libfs: Add simple_offset_empty()"
https://git.kernel.org/vfs/vfs/c/06ed2dfc3234
[3/5] Revert "libfs: fix infinite directory reads for offset dir"
https://git.kernel.org/vfs/vfs/c/29bc7ff8920d
[4/5] libfs: Replace simple_offset end-of-directory detection
https://git.kernel.org/vfs/vfs/c/d4849629a4b7
[5/5] libfs: Use d_children list to iterate simple_offset directories
https://git.kernel.org/vfs/vfs/c/5ba9a91ae23f
next prev parent reply other threads:[~2024-12-05 17:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 15:52 cel
2024-12-04 15:52 ` [PATCH v4 1/5] libfs: Return ENOSPC when the directory offset range is exhausted cel
2024-12-04 15:52 ` [PATCH v4 2/5] Revert "libfs: Add simple_offset_empty()" cel
2024-12-04 15:52 ` [PATCH v4 3/5] Revert "libfs: fix infinite directory reads for offset dir" cel
2024-12-04 15:52 ` [PATCH v4 4/5] libfs: Replace simple_offset end-of-directory detection cel
2024-12-04 15:52 ` [PATCH v4 5/5] libfs: Use d_children list to iterate simple_offset directories cel
2024-12-08 17:11 ` Chuck Lever
2024-12-14 17:13 ` Chuck Lever
2024-12-14 17:49 ` Al Viro
2024-12-14 19:22 ` Chuck Lever
2024-12-14 19:59 ` Al Viro
2024-12-05 17:09 ` Christian Brauner [this message]
2024-12-05 22:16 ` [PATCH v4 0/5] Improve simple directory offset wrap behavior Chuck Lever
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241205-jahre-geloben-8f47154d698e@brauner \
--to=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=hughd@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yangerkun@huaweicloud.com \
--cc=yukuai3@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox