From: Zhan Xusheng <zhanxusheng1024@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Joseph Qi <joseph.qi@linux.alibaba.com>
Cc: Jan Kara <jack@suse.cz>, Baokun Li <libaokun@linux.alibaba.com>,
Ojaswin Mujoo <ojaswin@linux.ibm.com>,
Ritesh Harjani <ritesh.list@gmail.com>,
Zhang Yi <yi.zhang@huawei.com>, Mark Fasheh <mark@fasheh.com>,
Joel Becker <jlbec@evilplan.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-ext4@vger.kernel.org, ocfs2-devel@lists.linux.dev,
linux-kernel@vger.kernel.org, zhanxusheng@xiaomi.com
Subject: [PATCH 0/2] fs: fix readdir position truncation on 32-bit kernels
Date: Thu, 6 Aug 2026 10:20:42 +0800 [thread overview]
Message-ID: <20260806022044.167962-1-zhanxusheng@xiaomi.com> (raw)
Both ext4 and ocfs2 rebuild the directory cookie in ->iterate with
ctx->pos = (ctx->pos & ~(sb->s_blocksize - 1)) | offset;
ctx->pos is loff_t (64-bit) but sb->s_blocksize is unsigned long. On
32-bit kernels unsigned long is 32-bit, so ~(sb->s_blocksize - 1) is a
32-bit value (e.g. 0xfffff000 for 4 KiB) and, under the usual arithmetic
conversions, is zero-extended to 0x00000000fffff000 in the AND with the
64-bit ctx->pos. The high 32 bits of ctx->pos are silently cleared even
though a directory may exceed 4 GiB.
When readdir() crosses the 4 GiB boundary on a 32-bit kernel the position
is reset back into the first 4 GiB, and the re-validation path then
re-enumerates already-returned dirents indefinitely.
These are the block-offset (non-hashed) readdir paths: ocfs2's
extent-list path (ocfs2_dir_foreach_blk_el(), used for all non-inline
directories) and ext4's linear path (non-indexed directories, or the
ext4_dx_readdir() ERR_BAD_DX_DIR fallback).
This is the same class of bug that commit 3dce5bb82c97 ("exfat: Fix
bitwise operation having different size") fixed in exfat. Cast the mask
operand to loff_t so the AND is performed in 64-bit. 64-bit kernels are
unaffected.
The two filesystems are independent; they are sent together only because
the bug and the fix are identical, so each maintainer can pick the
relevant patch. The truncation was verified with a freestanding 32-bit
test mirroring the expression; not reproduced on a live 32-bit >4 GiB
directory.
Zhan Xusheng (2):
ext4: fix readdir position truncation on 32-bit kernels
ocfs2: fix readdir position truncation on 32-bit kernels
fs/ext4/dir.c | 2 +-
fs/ocfs2/dir.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.43.0
next reply other threads:[~2026-08-06 2:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 2:20 Zhan Xusheng [this message]
2026-08-06 2:20 ` [PATCH 1/2] ext4: " Zhan Xusheng
2026-08-06 9:49 ` Jan Kara
2026-08-06 2:20 ` [PATCH 2/2] ocfs2: " Zhan Xusheng
2026-08-06 4:42 ` Andrew Morton
2026-08-06 10:23 ` Joseph Qi
2026-08-06 4:39 ` [PATCH 0/2] fs: " Andrew Morton
2026-08-06 12:19 ` Zhan Xusheng
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=20260806022044.167962-1-zhanxusheng@xiaomi.com \
--to=zhanxusheng1024@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=libaokun@linux.alibaba.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
--cc=yi.zhang@huawei.com \
--cc=zhanxusheng@xiaomi.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
all inboxes | Powered by JetHome®