* generic/471 failing on linux-next -- KI?
@ 2022-07-31 18:16 Theodore Ts'o
2022-07-31 22:59 ` Dave Chinner
0 siblings, 1 reply; 2+ messages in thread
From: Theodore Ts'o @ 2022-07-31 18:16 UTC (permalink / raw)
To: linux-fsdevel, linux-xfs, linux-ext4
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?
This test was *not* failing on a kernel based on 5.19-rc5, so it looks
like something that got added in linux-next.
- Ted
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: generic/471 failing on linux-next -- KI?
2022-07-31 18:16 generic/471 failing on linux-next -- KI? Theodore Ts'o
@ 2022-07-31 22:59 ` Dave Chinner
0 siblings, 0 replies; 2+ messages in thread
From: Dave Chinner @ 2022-07-31 22:59 UTC (permalink / raw)
To: Theodore Ts'o; +Cc: linux-fsdevel, linux-xfs, linux-ext4
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-07-31 22:59 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-07-31 18:16 generic/471 failing on linux-next -- KI? Theodore Ts'o
2022-07-31 22:59 ` Dave Chinner
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox