All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Moon Hee Lee <moonhee.lee.ca@gmail.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<linux-ext4@vger.kernel.org>, <tytso@mit.edu>,
	<adilger.kernel@dilger.ca>, <linux-kernel@vger.kernel.org>,
	<syzbot+544248a761451c0df72f@syzkaller.appspotmail.com>,
	<linux-kernel-mentees@lists.linux.dev>,
	<skhan@linuxfoundation.org>, <david.hunter.linux@gmail.com>,
	Moon Hee Lee <moonhee.lee.ca@gmail.com>, <oliver.sang@intel.com>
Subject: Re: [PATCH] ext4: bail out when EXT4_INLINE_DATA_FL lacks system.data xattr
Date: Tue, 22 Jul 2025 13:53:44 +0800	[thread overview]
Message-ID: <202507220717.738699fb-lkp@intel.com> (raw)
In-Reply-To: <20250710175837.29822-2-moonhee.lee.ca@gmail.com>



Hello,

kernel test robot noticed "xfstests.ext4.031.fail" on:

commit: ac16746132e9dafa56057ce201948e8853fd3834 ("[PATCH] ext4: bail out when EXT4_INLINE_DATA_FL lacks system.data xattr")
url: https://github.com/intel-lab-lkp/linux/commits/Moon-Hee-Lee/ext4-bail-out-when-EXT4_INLINE_DATA_FL-lacks-system-data-xattr/20250711-020009
base: https://git.kernel.org/cgit/linux/kernel/git/tytso/ext4.git dev
patch link: https://lore.kernel.org/all/20250710175837.29822-2-moonhee.lee.ca@gmail.com/
patch subject: [PATCH] ext4: bail out when EXT4_INLINE_DATA_FL lacks system.data xattr

in testcase: xfstests
version: xfstests-x86_64-e1e4a0ea-1_20250714
with following parameters:

	bp1_memmap: 4G!8G
	bp2_memmap: 4G!16G
	disk: 2pmem
	fs: ext4
	test: ext4-031


config: x86_64-rhel-9.4-func
compiler: gcc-12
test machine: 8 threads Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (Skylake) with 28G memory

(please refer to attached dmesg/kmsg for entire log/backtrace)


If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202507220717.738699fb-lkp@intel.com

2025-07-17 19:49:18 export TEST_DIR=/fs/pmem0
2025-07-17 19:49:18 export TEST_DEV=/dev/pmem0
2025-07-17 19:49:18 export FSTYP=ext4
2025-07-17 19:49:18 export SCRATCH_MNT=/fs/scratch
2025-07-17 19:49:18 mkdir /fs/scratch -p
2025-07-17 19:49:18 export SCRATCH_DEV=/dev/pmem1
2025-07-17 19:49:18 echo ext4/031
2025-07-17 19:49:18 ./check -E tests/exclude/ext4 ext4/031
FSTYP         -- ext4
PLATFORM      -- Linux/x86_64 lkp-skl-d01 6.15.0-rc4-00053-gac16746132e9 #1 SMP PREEMPT_DYNAMIC Fri Jul 18 03:31:11 CST 2025
MKFS_OPTIONS  -- -F /dev/pmem1
MOUNT_OPTIONS -- -o acl,user_xattr /dev/pmem1 /fs/scratch

ext4/031       - output mismatch (see /lkp/benchmarks/xfstests/results//ext4/031.out.bad)
    --- tests/ext4/031.out	2025-07-14 17:48:52.000000000 +0000
    +++ /lkp/benchmarks/xfstests/results//ext4/031.out.bad	2025-07-17 19:49:20.122098626 +0000
    @@ -1,2 +1,3 @@
     QA output created by 031
    +/lkp/benchmarks/xfstests/tests/ext4/031: line 35: echo: write error: Structure needs cleaning
     Silence is golden
    ...
    (Run 'diff -u /lkp/benchmarks/xfstests/tests/ext4/031.out /lkp/benchmarks/xfstests/results//ext4/031.out.bad'  to see the entire diff)
Ran: ext4/031
Failures: ext4/031
Failed 1 of 1 tests


The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250722/202507220717.738699fb-lkp@intel.com


-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


      reply	other threads:[~2025-07-22  5:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-10 17:58 [PATCH] ext4: bail out when EXT4_INLINE_DATA_FL lacks system.data xattr Moon Hee Lee
2025-07-22  5:53 ` kernel test robot [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=202507220717.738699fb-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=david.hunter.linux@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=moonhee.lee.ca@gmail.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=skhan@linuxfoundation.org \
    --cc=syzbot+544248a761451c0df72f@syzkaller.appspotmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.