Hi, this is your Linux kernel regression tracker. Top-posting for once,
to make this easily accessible to everyone.
As per recent general discussions with the 0-day folks, I'm dropping
below regression from the list of tracked issues, as this report didn't
gain any traction. That for example can happen if the developers
considered the regression of no practical relevance, as they assume it
only materializes in micro-benchmarks, is due to a broken test case, or
some fluke.
Not sure if that or something else is the reason why this particular
report didn't gain any traction, but I lack the bandwidth to follow-up
on each and every regression some CI system found and reported. At the
same time I don't want to keep these reports in the list of tracked
issues forever, as that creates noise and makes it harder to spot the
important issues in regzbot's reports and lists. That's why I hereby
remove it:
#regzbot invalid: 0-day report that didn't get traction; might be of no
relevance
Ciao, Thorsten
On 23.08.22 03:39, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-11):
>
> commit: 1aa91d9c993397858a50c433933ea119903fdea2 ("xfs: Add async
> buffered write support")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
> in testcase: xfstests
> version: xfstests-x86_64-c1144bf-1_20220808
> with following parameters:
>
> disk: 4HDD
> fs: xfs
> test: generic-group-23
> ucode: 0xf0
>
> test-description: xfstests is a regression test suite for xfs and other
> files ystems.
> test-url: git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
>
>
> on test machine: 4 threads Intel(R) Xeon(R) CPU E3-1225 v5 @ 3.30GHz
> (Skylake) with 16G memory
>
> caused below changes (please refer to attached dmesg/kmsg for entire
> log/backtrace):
>
>
> generic/471 - output mismatch (see
> /lkp/benchmarks/xfstests/results//generic/471.out.bad)
> --- tests/generic/471.out 2022-08-08 17:00:46.000000000 +0000
> +++ /lkp/benchmarks/xfstests/results//generic/471.out.bad
> 2022-08-22 16:16:45.895663503 +0000
> @@ -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
> ...
> (Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/471.out
> /lkp/benchmarks/xfstests/results//generic/471.out.bad' to see the
> entire diff)
>
>
> =========================================================================================
> tbox_group/testcase/rootfs/kconfig/compiler/disk/fs/test/ucode:
>
> lkp-skl-d06/xfstests/debian-11.1-x86_64-20220510.cgz/x86_64-rhel-8.3-func/gcc-11/4HDD/xfs/generic-group-23/0xf0
>
> commit:
> 9641506b2deed1 ("xfs: Specify lockmode when calling
> xfs_ilock_for_iomap()")
> 1aa91d9c993397 ("xfs: Add async buffered write support")
>
> 9641506b2deed1bb 1aa91d9c993397858a50c433933
> ---------------- ---------------------------
> fail:runs %reproduction fail:runs
> | | |
> :6 33% 2:2 xfstests.generic.471.fail
>
>
> If you fix the issue, kindly add following tag
> Reported-by: kernel test robot <yujie.liu@xxxxxxxxx>
>
>
> To reproduce:
>
> git clone https://github.com/intel/lkp-tests.git
> cd lkp-tests
> sudo bin/lkp install job.yaml # job file is attached
> in this email
> bin/lkp split-job --compatible job.yaml # generate the yaml file
> for lkp run
> sudo bin/lkp run generated-yaml-file
>
> # if come across any failure that blocks the test,
> # please remove ~/.lkp and /lkp dir to run from a clean state.
>
>
> #regzbot introduced: 1aa91d9c99
>
