From: cel@kernel.org
To: Hugh Dickens <hughd@google.com>,
Christian Brauner <brauner@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>
Cc: <linux-fsdevel@vger.kernel.org>, <linux-mm@kvack.org>,
yukuai3@huawei.com, yangerkun@huaweicloud.com,
Chuck Lever <chuck.lever@oracle.com>
Subject: [RFC PATCH v3 0/5] Improve simple directory offset wrap behavior
Date: Wed, 27 Nov 2024 10:28:10 -0500 [thread overview]
Message-ID: <20241127152815.151781-1-cel@kernel.org> (raw)
From: Chuck Lever <chuck.lever@oracle.com>
The purpose of this series is construct a set of upstream fixes that
can be backported to v6.6 to address CVE-2024-46701.
The v3 series updates yesterday's v2. Some bugs and review comments
have been addressed, and the rationale for reverting 64a7ce76fb90
("libfs: fix infinite directory reads for offset dir") has been
clarified.
v3 passes xfstests except for generic/637.
The series has been pushed to:
https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git/log/?h=tmpfs-fixes
Chuck Lever (5):
libfs: Return ENOSPC when the directory offset range is exhausted
libfs: Remove unnecessary locking from simple_offset_empty()
Revert "libfs: fix infinite directory reads for offset dir"
libfs: Refactor end-of-directory detection for simple_offset
directories
libfs: Refactor offset_iterate_dir()
fs/libfs.c | 145 +++++++++++++++++++++++++++++++++++++++--------------
1 file changed, 107 insertions(+), 38 deletions(-)
--
2.47.0
next reply other threads:[~2024-11-27 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 15:28 cel [this message]
2024-11-27 15:28 ` [RFC PATCH v3 1/5] libfs: Return ENOSPC when the directory offset range is exhausted cel
2024-11-27 15:28 ` [RFC PATCH v3 2/5] libfs: Remove unnecessary locking from simple_offset_empty() cel
2024-11-27 15:28 ` [RFC PATCH v3 3/5] Revert "libfs: fix infinite directory reads for offset dir" cel
2024-11-27 15:28 ` [RFC PATCH v3 4/5] libfs: Refactor end-of-directory detection for simple_offset directories cel
2024-11-27 15:28 ` [RFC PATCH v3 5/5] libfs: Refactor offset_iterate_dir() cel
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=20241127152815.151781-1-cel@kernel.org \
--to=cel@kernel.org \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.