From: Chuck Lever III <chuck.lever@oracle.com>
To: Hugh Dickins <hughd@google.com>
Cc: "Hong, Yifan" <jacky8hyf@gmail.com>,
Rob Landley <rob@landley.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
"bugzilla-daemon@kernel.org" <bugzilla-daemon@kernel.org>
Subject: Re: [Bug 219094] gen_kheaders.sh gets stuck in an infinite loop (on tmpfs)
Date: Fri, 26 Jul 2024 13:20:52 +0000 [thread overview]
Message-ID: <84DBD5CC-BFA9-497F-8545-48D181FCD517@oracle.com> (raw)
In-Reply-To: <a2808893-d257-e6b3-e168-0478d7255621@google.com>
> On Jul 25, 2024, at 9:05 PM, Hugh Dickins <hughd@google.com> wrote:
>
> Please send responses by email reply-to-all rather than through bugzilla.
>
> On Thu, 25 Jul 2024, bugzilla-daemon@kernel.org wrote:
>
>> https://bugzilla.kernel.org/show_bug.cgi?id=219094
>>
>> Hong, Yifan (jacky8hyf@gmail.com) reports:
>>
>> I have hit a similar bug to https://bugzilla.kernel.org/show_bug.cgi?id=217681, but on tmpfs.
>>
>> Here's a small reproducer for the bug, from https://bugzilla.kernel.org/show_bug.cgi?id=217681#c1:
>>
>> ```
>> #include <sys/types.h>
>> #include <dirent.h>
>> #include <stdio.h>
>>
>> int main(int argc, char *argv[])
>> {
>> DIR *dir = opendir(".");
>> struct dirent *dd;
>>
>> while ((dd = readdir(dir))) {
>> printf("%s\n", dd->d_name);
>> rename(dd->d_name, "TEMPFILE");
>> rename("TEMPFILE", dd->d_name);
>> }
>> closedir(dir);
>> }
>> ```
>>
>> Run in a directory with multiple (2000) files, it does not complete on tmpfs. I created a tmpfs mount point via
>>
>> ```
>> mount -o size=1G -t tmpfs none ~/tmpfs/mount/
>> ```
>>
>> The other bug was fixed on btrfs via https://lore.kernel.org/linux-btrfs/c9ceb0e15d92d0634600603b38965d9b6d986b6d.1691923900.git.fdmanana@suse.com/. Could anyone please see if the issue can be ported to tmpfs as well? Thanks in advance!
>>
>> I am using a `Linux version 6.6.15` kernel, if that's useful to anyone.
>
> Thank you for reporting, Yifan; and thank you for the easy reproducer, Rob.
>
> Yes, it appears that tmpfs was okay for this up to v6.5, but cannot cope
> from v6.6 onwards - a likely-sounding fix went into v6.10, but that must
> have been for something different, v6.10 still failing on this repro.
>
> Chuck, I'm hoping that you will have time to spare to solve this in latest;
> and then we shall want a backport (of only this fix, or more?) for v6.6 LTS.
Well, I don't have time, but I will indeed have a look. ;-)
This does look awfully similar to the rename bug I fixed
recently in this code.
Meanwhile, can I ask that someone else begin collecting these
reproducers to add to fstests? Christian and I have both run
fstests repeatedly against tmpfs and it does not seem to find
these corner cases.
--
Chuck Lever
prev parent reply other threads:[~2024-07-26 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-219094-5568@https.bugzilla.kernel.org/>
[not found] ` <bug-219094-5568-fyOeXKhNmt@https.bugzilla.kernel.org/>
2024-07-26 1:05 ` Hugh Dickins
2024-07-26 13:20 ` Chuck Lever III [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=84DBD5CC-BFA9-497F-8545-48D181FCD517@oracle.com \
--to=chuck.lever@oracle.com \
--cc=bugzilla-daemon@kernel.org \
--cc=hughd@google.com \
--cc=jacky8hyf@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rob@landley.net \
/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