From: yangerkun <yangerkun@huawei.com>
To: Filipe Manana <fdmanana@kernel.org>,
Christoph Hellwig <hch@infradead.org>, <chuck.lever@oracle.com>
Cc: <zlang@kernel.org>, <fstests@vger.kernel.org>,
<linux-mm@kvack.org>, <hughd@google.com>,
<akpm@linux-foundation.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] generic/736: don't run it on tmpfs
Date: Wed, 24 Jul 2024 21:30:57 +0800 [thread overview]
Message-ID: <4188b7b5-3576-9e5f-6297-794558d7a01e@huawei.com> (raw)
In-Reply-To: <CAL3q7H5AivAMSWk3FmmsrSqbeLfqMw_hr05b_Rdzk7hnnrsWiA@mail.gmail.com>
Hi, All,
Sorry for the delay relay(something happened, and cannot use pc
before...).
在 2024/7/21 1:26, Filipe Manana 写道:
> On Sat, Jul 20, 2024 at 9:38 AM Yang Erkun <yangerkun@huawei.com> wrote:
>>
>> We use offset_readdir for tmpfs, and every we call rename, the offset
>> for the parent dir will increase by 1. So for tmpfs we will always
>> fail since the infinite readdir.
>
> Having an infinite readdir sounds like a bug, or at least an
> inconvenience and surprising for users.
> We had that problem in btrfs which affected users/applications, see:
>
> https://lore.kernel.org/linux-btrfs/2c8c55ec-04c6-e0dc-9c5c-8c7924778c35@landley.net/
>
> which was surprising for them since every other filesystem they
> used/tested didn't have that problem.
> Why not fix tmpfs?
Thanks for all your advise, I will give a detail analysis first(maybe
until last week I can do it), and after we give a conclusion about does
this behavior a bug or something expected to occur, I will choose the
next step!
Thanks again for all your advise!
>
> Thanks.
>
>>
>> Signed-off-by: Yang Erkun <yangerkun@huawei.com>
>> ---
>> tests/generic/736 | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/tests/generic/736 b/tests/generic/736
>> index d2432a82..9fafa8df 100755
>> --- a/tests/generic/736
>> +++ b/tests/generic/736
>> @@ -18,7 +18,7 @@ _cleanup()
>> rm -fr $target_dir
>> }
>>
>> -_supported_fs generic
>> +_supported_fs generic ^tmpfs
>> _require_test
>> _require_test_program readdir-while-renames
>>
>> --
>> 2.39.2
>>
>>
next prev parent reply other threads:[~2024-07-24 13:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-20 8:35 Yang Erkun
2024-07-20 17:26 ` Filipe Manana
2024-07-24 13:30 ` yangerkun [this message]
2024-07-29 13:53 ` yangerkun
2024-07-29 14:21 ` Christoph Hellwig
2024-07-29 14:26 ` yangerkun
2024-07-29 14:29 ` Chuck Lever III
2024-07-29 17:35 ` Filipe Manana
2024-07-30 1:02 ` yangerkun
2024-07-29 14:32 ` Filipe Manana
2024-07-30 1:05 ` yangerkun
2024-07-22 14:21 ` Christoph Hellwig
2024-07-22 14:25 ` 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=4188b7b5-3576-9e5f-6297-794558d7a01e@huawei.com \
--to=yangerkun@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=chuck.lever@oracle.com \
--cc=fdmanana@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=hughd@google.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=zlang@kernel.org \
/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