From: Christian Brauner <brauner@kernel.org>
To: Yongjian Sun <sunyongjian@huaweicloud.com>
Cc: Christian Brauner <brauner@kernel.org>,
yangerkun@huawei.com, linux-fsdevel@vger.kernel.org,
linux-mm@vger.kernel.org
Subject: Re: [PATCH] libfs: Fix duplicate directory entry in offset_dir_lookup
Date: Thu, 20 Mar 2025 14:28:30 +0100 [thread overview]
Message-ID: <20250320-bersten-nippen-753e57fbae45@brauner> (raw)
In-Reply-To: <20250320034417.555810-1-sunyongjian@huaweicloud.com>
On Thu, 20 Mar 2025 11:44:17 +0800, Yongjian Sun wrote:
> There is an issue in the kernel:
>
> In tmpfs, when using the "ls" command to list the contents
> of a directory with a large number of files, glibc performs
> the getdents call in multiple rounds. If a concurrent unlink
> occurs between these getdents calls, it may lead to duplicate
> directory entries in the ls output. One possible reproduction
> scenario is as follows:
>
> [...]
Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes 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.fixes
[1/1] libfs: Fix duplicate directory entry in offset_dir_lookup
https://git.kernel.org/vfs/vfs/c/f70681e9e606
prev parent reply other threads:[~2025-03-20 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 3:44 [PATCH] libfs: Fix duplicate directory entry in offset_dir_lookup Yongjian Sun
2025-03-20 13:12 ` Chuck Lever
2025-03-20 13:28 ` Christian Brauner [this message]
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=20250320-bersten-nippen-753e57fbae45@brauner \
--to=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@vger.kernel.org \
--cc=sunyongjian@huaweicloud.com \
--cc=yangerkun@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;
as well as URLs for NNTP newsgroup(s).