From: "Si, Beibei" <beibei.si@intel.com>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: "Li, Philip" <philip.li@intel.com>,
"Sang, Oliver" <oliver.sang@intel.com>,
"Si, Beibei" <beibei.si@intel.com>
Subject: RE: [loop] efcfec579f: mdadm-selftests.12imsm-r0_2d-grow-r0_3d.fail #forregzbot
Date: Wed, 10 Aug 2022 05:44:48 +0000 [thread overview]
Message-ID: <BN6PR11MB1729F27147FBD06FDED3F355FB659@BN6PR11MB1729.namprd11.prod.outlook.com> (raw)
#regzbot ^introduced efcfec579f
#regzbot title [loop] efcfec579f: mdadm-selftests.12imsm-r0_2d-grow-r0_3d.fail
> -----Original Message-----
> From: Sang, Oliver <oliver.sang@intel.com>
> Sent: Monday, August 8, 2022 10:42 PM
> To: Darrick J. Wong <darrick.wong@oracle.com>
> Cc: Jens Axboe <axboe@kernel.dk>; Christoph Hellwig <hch@lst.de>; LKML
> <linux-kernel@vger.kernel.org>; linux-block@vger.kernel.org; lkp@lists.01.org;
> lkp <lkp@intel.com>; regressions@lists.linux.dev
> Subject: [loop] efcfec579f: mdadm-selftests.12imsm-r0_2d-grow-r0_3d.fail
>
>
> (pleased be noted we found the issue still exists on latest maineline, so report
> though the commit is old, FYI)
>
>
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-11):
>
> commit: efcfec579f6139528c9e6925eca2bc4a36da65c6 ("loop: fix no-unmap
> write-zeroes request behavior")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
> in testcase: mdadm-selftests
> version: mdadm-selftests-x86_64-5f41845-1_20220518
> with following parameters:
>
> disk: 1HDD
> test_prefix: 12
> ucode: 0x28
>
>
>
> on test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-4790T CPU @ 2.70GHz
> with 16G memory
>
> caused below changes (please refer to attached dmesg/kmsg for entire
> log/backtrace):
>
>
>
>
> If you fix the issue, kindly add following tag
> Reported-by: kernel test robot <oliver.sang@intel.com>
>
> 2022-08-05 18:01:28 mkdir -p /var/tmp
> 2022-08-05 18:01:28 mke2fs -t ext3 -b 4096 -J size=4 -q /dev/sda1
> 2022-08-05 18:02:00 mount -t ext3 /dev/sda1 /var/tmp sed -e
> 's/{DEFAULT_METADATA}/1.2/g' \ -e 's,{MAP_PATH},/run/mdadm/map,g'
> mdadm.8.in > mdadm.8 /usr/bin/install -D -m 644 mdadm.8
> /usr/share/man/man8/mdadm.8 /usr/bin/install -D -m 644 mdmon.8
> /usr/share/man/man8/mdmon.8 /usr/bin/install -D -m 644 md.4
> /usr/share/man/man4/md.4 /usr/bin/install -D -m 644 mdadm.conf.5
> /usr/share/man/man5/mdadm.conf.5 /usr/bin/install -D -m 644 udev-md-raid-
> creating.rules /lib/udev/rules.d/01-md-raid-creating.rules
> /usr/bin/install -D -m 644 udev-md-raid-arrays.rules /lib/udev/rules.d/63-md-
> raid-arrays.rules
> /usr/bin/install -D -m 644 udev-md-raid-assembly.rules /lib/udev/rules.d/64-md-
> raid-assembly.rules
> /usr/bin/install -D -m 644 udev-md-clustered-confirm-device.rules
> /lib/udev/rules.d/69-md-clustered-confirm-device.rules
> /usr/bin/install -D -m 755 mdadm /sbin/mdadm /usr/bin/install -D -m 755
> mdmon /sbin/mdmon Testing on linux-5.4.0-rc2-00010-gefcfec579f6139 kernel
> /lkp/benchmarks/mdadm-selftests/tests/12imsm-r0_2d-grow-r0_3d...
> ERROR: dmesg prints errors when testing 12imsm-r0_2d-grow-r0_3d!
>
> FAILED - see /var/tmp/12imsm-r0_2d-grow-r0_3d.log and /var/tmp/fail12imsm-
> r0_2d-grow-r0_3d.log for details Testing on linux-5.4.0-rc2-00010-
> gefcfec579f6139 kernel /lkp/benchmarks/mdadm-selftests/tests/12imsm-
> r0_2d-grow-r0_4d...
> ERROR: dmesg prints errors when testing 12imsm-r0_2d-grow-r0_4d!
>
> FAILED - see /var/tmp/12imsm-r0_2d-grow-r0_4d.log and /var/tmp/fail12imsm-
> r0_2d-grow-r0_4d.log for details Testing on linux-5.4.0-rc2-00010-
> gefcfec579f6139 kernel /lkp/benchmarks/mdadm-selftests/tests/12imsm-
> r0_2d-grow-r0_5d...
> ERROR: dmesg prints errors when testing 12imsm-r0_2d-grow-r0_5d!
>
> FAILED - see /var/tmp/12imsm-r0_2d-grow-r0_5d.log and /var/tmp/fail12imsm-
> r0_2d-grow-r0_5d.log for details Testing on linux-5.4.0-rc2-00010-
> gefcfec579f6139 kernel /lkp/benchmarks/mdadm-selftests/tests/12imsm-
> r0_3d-grow-r0_4d...
> ERROR: dmesg prints errors when testing 12imsm-r0_3d-grow-r0_4d!
>
> FAILED - see /var/tmp/12imsm-r0_3d-grow-r0_4d.log and /var/tmp/fail12imsm-
> r0_3d-grow-r0_4d.log for details Testing on linux-5.4.0-rc2-00010-
> gefcfec579f6139 kernel /lkp/benchmarks/mdadm-selftests/tests/12imsm-
> r5_3d-grow-r5_4d... succeeded Testing on linux-5.4.0-rc2-00010-
> gefcfec579f6139 kernel /lkp/benchmarks/mdadm-selftests/tests/12imsm-
> r5_3d-grow-r5_5d... succeeded
>
>
>
> 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: efcfec579f
>
> --
> 0-DAY CI Kernel Test Service
> https://01.org/lkp
>
next reply other threads:[~2022-08-10 5:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 5:44 Si, Beibei [this message]
2022-08-15 13:19 ` [loop] efcfec579f: mdadm-selftests.12imsm-r0_2d-grow-r0_3d.fail #forregzbot Thorsten Leemhuis
2022-09-01 13:53 ` Philip Li
2022-09-02 11:23 ` Thorsten Leemhuis
2022-09-02 12:31 ` Philip Li
-- strict thread matches above, loose matches on Subject: below --
2022-08-08 14:42 [loop] efcfec579f: mdadm-selftests.12imsm-r0_2d-grow-r0_3d.fail kernel test robot
2022-09-08 13:17 ` [loop] efcfec579f: mdadm-selftests.12imsm-r0_2d-grow-r0_3d.fail #forregzbot 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=BN6PR11MB1729F27147FBD06FDED3F355FB659@BN6PR11MB1729.namprd11.prod.outlook.com \
--to=beibei.si@intel.com \
--cc=oliver.sang@intel.com \
--cc=philip.li@intel.com \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).