From: "Theodore Ts'o" <tytso@mit.edu>
To: Jens Axboe <axboe@kernel.dk>
Cc: "Andres Freund" <andres@anarazel.de>,
"Dave Chinner" <david@fromorbit.com>,
"Thorsten Leemhuis" <regressions@leemhuis.info>,
"Shreeya Patel" <shreeya.patel@collabora.com>,
linux-ext4@vger.kernel.org,
"Ricardo Cañuelo" <ricardo.canuelo@collabora.com>,
gustavo.padovan@collabora.com, zsm@google.com,
garrick@google.com,
"Linux regressions mailing list" <regressions@lists.linux.dev>,
io-uring@vger.kernel.org
Subject: Re: task hung in ext4_fallocate #2
Date: Wed, 25 Oct 2023 15:55:39 -0400 [thread overview]
Message-ID: <20231025195539.GA2897448@mit.edu> (raw)
In-Reply-To: <b5578447-81f6-4207-b83d-812da7c981a5@kernel.dk>
On Wed, Oct 25, 2023 at 09:36:01AM -0600, Jens Axboe wrote:
>
> FWIW, I wrote a small test case which does seem to trigger it very fast,
> as expected:
Great! I was about to ask if we had an easy reproducer. Any chance
you can package this up as an test in xfstests? Or would you like
some help with that?
Thanks,
- Ted
next prev parent reply other threads:[~2023-10-25 19:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 3:37 task hung in ext4_fallocate #2 Andres Freund
2023-10-18 0:43 ` Theodore Ts'o
2023-10-18 2:50 ` Andres Freund
2023-10-18 9:41 ` Andres Freund
2023-10-24 1:12 ` Dave Chinner
2023-10-24 1:36 ` Andres Freund
2023-10-24 14:30 ` Jens Axboe
2023-10-24 18:35 ` Jens Axboe
2023-10-25 0:06 ` Dave Chinner
2023-10-25 0:34 ` Jens Axboe
2023-10-25 15:31 ` Andres Freund
2023-10-25 15:36 ` Jens Axboe
2023-10-25 16:14 ` Andres Freund
2023-10-26 2:48 ` Andres Freund
2023-10-25 19:55 ` Theodore Ts'o [this message]
2023-10-25 22:28 ` Dave Chinner
2023-10-20 7:01 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-10-29 6:28 ` Linux regression tracking #update (Thorsten Leemhuis)
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=20231025195539.GA2897448@mit.edu \
--to=tytso@mit.edu \
--cc=andres@anarazel.de \
--cc=axboe@kernel.dk \
--cc=david@fromorbit.com \
--cc=garrick@google.com \
--cc=gustavo.padovan@collabora.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=ricardo.canuelo@collabora.com \
--cc=shreeya.patel@collabora.com \
--cc=zsm@google.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