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,
Liam.Howlett@oracle.com, Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH v7 0/5] Improve simple directory offset wrap behavior
Date: Sat, 28 Dec 2024 12:55:16 -0500 [thread overview]
Message-ID: <20241228175522.1854234-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.
In response to a reported failure of libhugetlbfs-test.32bit.gethugepagesizes:
https://lore.kernel.org/linux-fsdevel/f996eec0-30e1-4fbf-a936-49f3bedc09e9@oracle.com/T/#t
I've narrowed the range of directory offset values returned by
simple_offset_add() to 3 .. (S32_MAX - 1) on all platforms. This
means the allocation behavior is identical on 32-bit systems, 64-bit
systems, and 32-bit user space on 64-bit kernels. The new range
still permits over 2 billion concurrent entries per directory.
Changes since v6:
- Restrict the directory offset value range to S32_MAX on all platforms
This series (against v6.13-rc4) 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 | 162 +++++++++++++++++++++------------------------
include/linux/fs.h | 1 -
mm/shmem.c | 4 +-
3 files changed, 79 insertions(+), 88 deletions(-)
--
2.47.0
next reply other threads:[~2024-12-28 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-28 17:55 cel [this message]
2024-12-28 17:55 ` [PATCH v7 1/5] libfs: Return ENOSPC when the directory offset range is exhausted cel
2024-12-28 17:55 ` [PATCH v7 2/5] Revert "libfs: Add simple_offset_empty()" cel
2024-12-28 17:55 ` [PATCH v7 3/5] Revert "libfs: fix infinite directory reads for offset dir" cel
2024-12-28 17:55 ` [PATCH v7 4/5] libfs: Replace simple_offset end-of-directory detection cel
2024-12-28 17:55 ` [PATCH v7 5/5] libfs: Use d_children list to iterate simple_offset directories cel
2025-01-04 9:16 ` [PATCH v7 0/5] Improve simple directory offset wrap behavior Christian Brauner
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=20241228175522.1854234-1-cel@kernel.org \
--to=cel@kernel.org \
--cc=Liam.Howlett@oracle.com \
--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