From: Greg KH <gregkh@linuxfoundation.org>
To: ciprietti@google.com
Cc: stable@vger.kernel.org, yangerkun <yangerkun@huawei.com>,
Chuck Lever <chuck.lever@oracle.com>,
Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH] libfs: fix infinite directory reads for offset dir
Date: Tue, 28 Jan 2025 18:11:49 +0100 [thread overview]
Message-ID: <2025012819-goal-elastic-e89f@gregkh> (raw)
In-Reply-To: <20250128150322.2242111-1-ciprietti@google.com>
On Tue, Jan 28, 2025 at 03:03:22PM +0000, ciprietti@google.com wrote:
> From: yangerkun <yangerkun@huawei.com>
>
> [ Upstream commit 64a7ce76fb901bf9f9c36cf5d681328fc0fd4b5a ]
>
> After we switch tmpfs dir operations from simple_dir_operations to
> simple_offset_dir_operations, every rename happened will fill new dentry
> to dest dir's maple tree(&SHMEM_I(inode)->dir_offsets->mt) with a free
> key starting with octx->newx_offset, and then set newx_offset equals to
> free key + 1. This will lead to infinite readdir combine with rename
> happened at the same time, which fail generic/736 in xfstests(detail show
> as below).
>
> 1. create 5000 files(1 2 3...) under one dir
> 2. call readdir(man 3 readdir) once, and get one entry
> 3. rename(entry, "TEMPFILE"), then rename("TEMPFILE", entry)
> 4. loop 2~3, until readdir return nothing or we loop too many
> times(tmpfs break test with the second condition)
>
> We choose the same logic what commit 9b378f6ad48cf ("btrfs: fix infinite
> directory reads") to fix it, record the last_index when we open dir, and
> do not emit the entry which index >= last_index. The file->private_data
> now used in offset dir can use directly to do this, and we also update
> the last_index when we llseek the dir file.
>
> Fixes: a2e459555c5f ("shmem: stable directory offsets")
> Signed-off-by: yangerkun <yangerkun@huawei.com>
> Link: https://lore.kernel.org/r/20240731043835.1828697-1-yangerkun@huawei.com
> Reviewed-by: Chuck Lever <chuck.lever@oracle.com>
> [brauner: only update last_index after seek when offset is zero like Jan suggested]
> Signed-off-by: Christian Brauner <brauner@kernel.org>
> Signed-off-by: Andrea Ciprietti <ciprietti@google.com>
You forgot to mention what you changed.
> ---
> fs/libfs.c | 39 ++++++++++++++++++++++++++++-----------
> 1 file changed, 28 insertions(+), 11 deletions(-)
>
> diff --git a/fs/libfs.c b/fs/libfs.c
> index dc0f7519045f..916c39e758b1 100644
> --- a/fs/libfs.c
> +++ b/fs/libfs.c
> @@ -371,6 +371,15 @@ void simple_offset_destroy(struct offset_ctx *octx)
> xa_destroy(&octx->xa);
> }
>
> +static int offset_dir_open(struct inode *inode, struct file *file)
> +{
> + struct offset_ctx *ctx = inode->i_op->get_offset_ctx(inode);
> + unsigned long next_offset = (unsigned long)ctx->next_offset;
> +
> + file->private_data = (void *)next_offset;
Why do you need 2 casts here when the original did not?
thanks,
greg k-h
next prev parent reply other threads:[~2025-01-28 17:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 15:03 [PATCH] libfs: fix infinite directory reads for offset dir ciprietti
2025-01-28 15:51 ` Chuck Lever
2025-01-28 16:17 ` Sasha Levin
2025-01-28 17:11 ` Greg KH [this message]
2025-01-28 17:12 ` Greg KH
2025-01-28 17:17 ` Chuck Lever
[not found] ` <CA+PG2H1tRRJkWBVdsiA1fcqYyVMdOPauJqx-HJKhXdwxK9frJg@mail.gmail.com>
2025-01-29 13:38 ` Andrea Ciprietti
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=2025012819-goal-elastic-e89f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=ciprietti@google.com \
--cc=stable@vger.kernel.org \
--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