From: Christoph Hellwig <hch@infradead.org>
To: cel@kernel.org
Cc: Hugh Dickens <hughd@google.com>,
Christian Brauner <brauner@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
yukuai3@huawei.com, yangerkun@huaweicloud.com,
Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [RFC PATCH v2 0/5] Improve simple directory offset wrap behavior
Date: Tue, 26 Nov 2024 08:24:28 -0800 [thread overview]
Message-ID: <Z0X2PAZy04JGjjFN@infradead.org> (raw)
In-Reply-To: <20241126155444.2556-1-cel@kernel.org>
On Tue, Nov 26, 2024 at 10:54:39AM -0500, cel@kernel.org wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
>
> This series attempts to narrow some gaps in the current tmpfs
> directory offset mechanism that relate to misbehaviors reported by
> Yu Kuai <yukuai3@huawei.com> and Yang Erkun <yangerkun@huawei.com>.
Any chance you could write xfstests test cases to exercise these
corner cases?
next prev parent reply other threads:[~2024-11-26 16:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 15:54 cel
2024-11-26 15:54 ` [RFC PATCH v2 1/5] libfs: Return ENOSPC when the directory offset range is exhausted cel
2024-11-27 3:11 ` yangerkun
2024-11-26 15:54 ` [RFC PATCH v2 2/5] libfs: Check dentry before locking in simple_offset_empty() cel
2024-11-27 3:09 ` yangerkun
2024-11-27 14:36 ` Chuck Lever
2024-11-29 8:17 ` yangerkun
2024-11-30 17:03 ` Chuck Lever
2024-11-26 15:54 ` [RFC PATCH v2 3/5] Revert "libfs: fix infinite directory reads for offset dir" cel
2024-11-26 15:54 ` [RFC PATCH v2 4/5] libfs: Refactor end-of-directory detection for simple_offset directories cel
2024-11-26 15:54 ` [RFC PATCH v2 5/5] libfs: Refactor offset_iterate_dir() cel
2024-11-26 16:24 ` Christoph Hellwig [this message]
2024-11-26 16:59 ` [RFC PATCH v2 0/5] Improve simple directory offset wrap behavior Chuck Lever III
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=Z0X2PAZy04JGjjFN@infradead.org \
--to=hch@infradead.org \
--cc=brauner@kernel.org \
--cc=cel@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