lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 31 Jul 2022 14:16:34 -0400 From: "Theodore Ts'o" <tytso@....edu> To: linux-fsdevel@...r.kernel.org, linux-xfs@...r.kernel.org, linux-ext4@...r.kernel.org Subject: generic/471 failing on linux-next -- KI? 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
Powered by blists - more mailing lists