From: Dave Chinner <david@fromorbit.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-ext4@vger.kernel.org
Subject: Re: generic/471 failing on linux-next -- KI?
Date: Mon, 1 Aug 2022 08:59:01 +1000 [thread overview]
Message-ID: <20220731225901.GY3600936@dread.disaster.area> (raw)
In-Reply-To: <YubHAqTCPvNj10Mx@mit.edu>
On Sun, Jul 31, 2022 at 02:16:34PM -0400, Theodore Ts'o wrote:
> I was just doing a last test of ext4 merged with linux-next before the
> merge window opened, and I noticed generic/471 is now failing. After
> some more investigation it's failing for xfs and ext4, with the same
> problem:
>
> --- tests/generic/471.out 2022-07-31 00:02:23.000000000 -0400
> +++ /results/xfs/results-4k/generic/471.out.bad 2022-07-31 14:11:47.045330411 0
> @@ -2,12 +2,10 @@
> pwrite: Resource temporarily unavailable
> wrote 8388608/8388608 bytes at offset 0
> XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> -RWF_NOWAIT time is within limits.
> +pwrite: Resource temporarily unavailable
> +(standard_in) 1: syntax error
> +RWF_NOWAIT took seconds
> ...
>
> I haven't had a chance to bisect this yet, and for a day or two --- so
> I figured I would ask --- is this a known issue?
Might have something to do with this set of changes:
https://lore.kernel.org/io-uring/c737af00-e879-fe01-380c-ba95b555f423@kernel.dk/
as it adds new places in the VFS that check for IOCB_NOWAIT. Pretty
sure it triggers -EAGAIN on timestamp updates now (in
file_modified() calls), which is probably what is happening here....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2022-07-31 22:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 18:16 generic/471 failing on linux-next -- KI? Theodore Ts'o
2022-07-31 22:59 ` Dave Chinner [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=20220731225901.GY3600936@dread.disaster.area \
--to=david@fromorbit.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
/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