From: cel@kernel.org
To: Hugh Dickins <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: [PATCH v5 0/5] Improve simple directory offset wrap behavior
Date: Sun, 15 Dec 2024 13:58:11 -0500 [thread overview]
Message-ID: <20241215185816.1826975-1-cel@kernel.org> (raw)
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.
Changes since v4:
- Refactor and rename find_next_sibling_locked()
This series (against v6.13-rc2) 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
Revert "libfs: Add simple_offset_empty()"
Revert "libfs: fix infinite directory reads for offset dir"
libfs: Replace simple_offset end-of-directory detection
libfs: Use d_children list to iterate simple_offset directories
fs/libfs.c | 163 ++++++++++++++++++++++-----------------------
include/linux/fs.h | 1 -
mm/shmem.c | 4 +-
3 files changed, 81 insertions(+), 87 deletions(-)
--
2.47.0
next reply other threads:[~2024-12-15 18:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 18:58 cel [this message]
2024-12-15 18:58 ` [PATCH v5 1/5] libfs: Return ENOSPC when the directory offset range is exhausted cel
2024-12-15 19:35 ` David Laight
2024-12-16 13:39 ` Pratyush Yadav
2024-12-16 13:51 ` Chuck Lever
2024-12-15 18:58 ` [PATCH v5 2/5] Revert "libfs: Add simple_offset_empty()" cel
2024-12-15 18:58 ` [PATCH v5 3/5] Revert "libfs: fix infinite directory reads for offset dir" cel
2024-12-15 18:58 ` [PATCH v5 4/5] libfs: Replace simple_offset end-of-directory detection cel
2024-12-15 18:58 ` [PATCH v5 5/5] libfs: Use d_children list to iterate simple_offset directories 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=20241215185816.1826975-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox