From: kernel test robot <oliver.sang@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-btrfs@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<linux-nfs@vger.kernel.org>, <devel@lists.orangefs.org>,
<linux-mtd@lists.infradead.org>,
"Christian Brauner" <brauner@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
David Sterba <dsterba@suse.com>, Jan Kara <jack@suse.cz>,
Mike Marshall <hubcap@omnibond.com>,
Martin Brandenburg <martin@omnibond.com>,
"Carlos Maiolino" <cem@kernel.org>, Stefan Roesch <shr@fb.com>,
Jeff Layton <jlayton@kernel.org>, <linux-kernel@vger.kernel.org>,
<gfs2@lists.linux.dev>, <io-uring@vger.kernel.org>,
<linux-unionfs@vger.kernel.org>, <linux-xfs@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: Re: [PATCH 05/11] fs: return I_DIRTY_* and allow error returns from inode_update_timestamps
Date: Mon, 29 Dec 2025 15:27:33 +0800 [thread overview]
Message-ID: <202512291537.9abd5523-lkp@intel.com> (raw)
In-Reply-To: <20251223003756.409543-6-hch@lst.de>
Hello,
kernel test robot noticed "xfstests.generic.324.fail" on:
commit: 515788c3eccaa35a6a34f8eed75e2a598172dcb0 ("[PATCH 05/11] fs: return I_DIRTY_* and allow error returns from inode_update_timestamps")
url: https://github.com/intel-lab-lkp/linux/commits/Christoph-Hellwig/fs-allow-error-returns-from-generic_update_time/20251223-093805
base: https://git.kernel.org/cgit/fs/xfs/xfs-linux.git for-next
patch link: https://lore.kernel.org/all/20251223003756.409543-6-hch@lst.de/
patch subject: [PATCH 05/11] fs: return I_DIRTY_* and allow error returns from inode_update_timestamps
in testcase: xfstests
version: xfstests-x86_64-a668057f-1_20251209
with following parameters:
disk: 4HDD
fs: btrfs
test: generic-324
config: x86_64-rhel-9.4-func
compiler: gcc-14
test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (Skylake) with 32G 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/202512291537.9abd5523-lkp@intel.com
2025-12-27 02:57:30 cd /lkp/benchmarks/xfstests
2025-12-27 02:57:30 export TEST_DIR=/fs/sdb1
2025-12-27 02:57:30 export TEST_DEV=/dev/sdb1
2025-12-27 02:57:30 export FSTYP=btrfs
2025-12-27 02:57:30 export SCRATCH_MNT=/fs/scratch
2025-12-27 02:57:30 mkdir /fs/scratch -p
2025-12-27 02:57:30 export SCRATCH_DEV_POOL="/dev/sdb2 /dev/sdb3 /dev/sdb4"
2025-12-27 02:57:30 echo generic/324
2025-12-27 02:57:30 ./check generic/324
FSTYP -- btrfs
PLATFORM -- Linux/x86_64 lkp-skl-d02 6.19.0-rc1-00022-g515788c3ecca #1 SMP PREEMPT_DYNAMIC Sat Dec 27 10:49:51 CST 2025
MKFS_OPTIONS -- /dev/sdb2
MOUNT_OPTIONS -- /dev/sdb2 /fs/scratch
generic/324 [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//generic/324.out.bad)
--- tests/generic/324.out 2025-12-09 15:20:52.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//generic/324.out.bad 2025-12-27 02:57:33.966266526 +0000
@@ -22,2509 +22,5 @@
XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
Before: in_range(10, 40)
After: in_range(1, -1)
-Defragment file with 250 * 2 fragments
-wrote 1234/1234 bytes at offset 0
-XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-wrote 1234/1234 bytes at offset 123400
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/324.out /lkp/benchmarks/xfstests/results//generic/324.out.bad' to see the entire diff)
Ran: generic/324
Failures: generic/324
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20251229/202512291537.9abd5523-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <oliver.sang@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-btrfs@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<linux-nfs@vger.kernel.org>, <devel@lists.orangefs.org>,
<linux-mtd@lists.infradead.org>,
"Christian Brauner" <brauner@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
David Sterba <dsterba@suse.com>, Jan Kara <jack@suse.cz>,
Mike Marshall <hubcap@omnibond.com>,
Martin Brandenburg <martin@omnibond.com>,
"Carlos Maiolino" <cem@kernel.org>, Stefan Roesch <shr@fb.com>,
Jeff Layton <jlayton@kernel.org>, <linux-kernel@vger.kernel.org>,
<gfs2@lists.linux.dev>, <io-uring@vger.kernel.org>,
<linux-unionfs@vger.kernel.org>, <linux-xfs@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: Re: [PATCH 05/11] fs: return I_DIRTY_* and allow error returns from inode_update_timestamps
Date: Mon, 29 Dec 2025 15:27:33 +0800 [thread overview]
Message-ID: <202512291537.9abd5523-lkp@intel.com> (raw)
In-Reply-To: <20251223003756.409543-6-hch@lst.de>
Hello,
kernel test robot noticed "xfstests.generic.324.fail" on:
commit: 515788c3eccaa35a6a34f8eed75e2a598172dcb0 ("[PATCH 05/11] fs: return I_DIRTY_* and allow error returns from inode_update_timestamps")
url: https://github.com/intel-lab-lkp/linux/commits/Christoph-Hellwig/fs-allow-error-returns-from-generic_update_time/20251223-093805
base: https://git.kernel.org/cgit/fs/xfs/xfs-linux.git for-next
patch link: https://lore.kernel.org/all/20251223003756.409543-6-hch@lst.de/
patch subject: [PATCH 05/11] fs: return I_DIRTY_* and allow error returns from inode_update_timestamps
in testcase: xfstests
version: xfstests-x86_64-a668057f-1_20251209
with following parameters:
disk: 4HDD
fs: btrfs
test: generic-324
config: x86_64-rhel-9.4-func
compiler: gcc-14
test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (Skylake) with 32G 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/202512291537.9abd5523-lkp@intel.com
2025-12-27 02:57:30 cd /lkp/benchmarks/xfstests
2025-12-27 02:57:30 export TEST_DIR=/fs/sdb1
2025-12-27 02:57:30 export TEST_DEV=/dev/sdb1
2025-12-27 02:57:30 export FSTYP=btrfs
2025-12-27 02:57:30 export SCRATCH_MNT=/fs/scratch
2025-12-27 02:57:30 mkdir /fs/scratch -p
2025-12-27 02:57:30 export SCRATCH_DEV_POOL="/dev/sdb2 /dev/sdb3 /dev/sdb4"
2025-12-27 02:57:30 echo generic/324
2025-12-27 02:57:30 ./check generic/324
FSTYP -- btrfs
PLATFORM -- Linux/x86_64 lkp-skl-d02 6.19.0-rc1-00022-g515788c3ecca #1 SMP PREEMPT_DYNAMIC Sat Dec 27 10:49:51 CST 2025
MKFS_OPTIONS -- /dev/sdb2
MOUNT_OPTIONS -- /dev/sdb2 /fs/scratch
generic/324 [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//generic/324.out.bad)
--- tests/generic/324.out 2025-12-09 15:20:52.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//generic/324.out.bad 2025-12-27 02:57:33.966266526 +0000
@@ -22,2509 +22,5 @@
XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
Before: in_range(10, 40)
After: in_range(1, -1)
-Defragment file with 250 * 2 fragments
-wrote 1234/1234 bytes at offset 0
-XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-wrote 1234/1234 bytes at offset 123400
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/324.out /lkp/benchmarks/xfstests/results//generic/324.out.bad' to see the entire diff)
Ran: generic/324
Failures: generic/324
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20251229/202512291537.9abd5523-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2025-12-29 7:27 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 0:37 re-enable IOCB_NOWAIT writes to files v4 Christoph Hellwig
2025-12-23 0:37 ` Christoph Hellwig
2025-12-23 0:37 ` [PATCH 01/11] fs: remove inode_update_time Christoph Hellwig
2025-12-23 0:37 ` Christoph Hellwig
2025-12-23 0:37 ` [PATCH 02/11] fs: allow error returns from generic_update_time Christoph Hellwig
2025-12-23 0:37 ` Christoph Hellwig
2025-12-23 0:37 ` [PATCH 03/11] fs: exit early in generic_update_time when there is no work Christoph Hellwig
2025-12-23 0:37 ` Christoph Hellwig
2025-12-23 5:33 ` Chaitanya Kulkarni
2025-12-23 5:33 ` Chaitanya Kulkarni
2025-12-23 0:37 ` [PATCH 04/11] fs: delay the actual timestamp updates in inode_update_timestamps Christoph Hellwig
2025-12-23 0:37 ` Christoph Hellwig
2025-12-23 5:35 ` Chaitanya Kulkarni
2025-12-23 5:35 ` Chaitanya Kulkarni
2025-12-23 0:37 ` [PATCH 05/11] fs: return I_DIRTY_* and allow error returns from inode_update_timestamps Christoph Hellwig
2025-12-23 0:37 ` Christoph Hellwig
2025-12-23 5:36 ` Chaitanya Kulkarni
2025-12-23 5:36 ` Chaitanya Kulkarni
2025-12-29 7:27 ` kernel test robot [this message]
2025-12-29 7:27 ` kernel test robot
2025-12-23 0:37 ` [PATCH 06/11] fs: factor out a sync_lazytime helper Christoph Hellwig
2025-12-23 0:37 ` Christoph Hellwig
2025-12-23 5:36 ` Chaitanya Kulkarni
2025-12-23 5:36 ` Chaitanya Kulkarni
2025-12-23 0:37 ` [PATCH 07/11] fs: add a ->sync_lazytime method Christoph Hellwig
2025-12-23 0:37 ` Christoph Hellwig
2025-12-23 5:37 ` Chaitanya Kulkarni
2025-12-23 5:37 ` Chaitanya Kulkarni
2025-12-23 0:37 ` [PATCH 08/11] fs: add support for non-blocking timestamp updates Christoph Hellwig
2025-12-23 0:37 ` Christoph Hellwig
2025-12-23 5:38 ` Chaitanya Kulkarni
2025-12-23 5:38 ` Chaitanya Kulkarni
2025-12-23 0:37 ` [PATCH 09/11] fat: enable " Christoph Hellwig
2025-12-23 0:37 ` Christoph Hellwig
2025-12-23 0:37 ` [PATCH 10/11] xfs: implement ->sync_lazytime Christoph Hellwig
2025-12-23 0:37 ` Christoph Hellwig
2025-12-23 0:37 ` [PATCH 11/11] xfs: enable non-blocking timestamp updates Christoph Hellwig
2025-12-23 0:37 ` Christoph Hellwig
2025-12-23 5:39 ` Chaitanya Kulkarni
2025-12-23 5:39 ` Chaitanya Kulkarni
2025-12-23 22:53 ` re-enable IOCB_NOWAIT writes to files v4 Christoph Hellwig
2025-12-23 22:53 ` Christoph Hellwig
2025-12-24 13:11 ` Christian Brauner
2025-12-24 13:11 ` Christian Brauner
2026-01-06 6:24 ` Christoph Hellwig
2026-01-06 6:24 ` Christoph Hellwig
2026-01-06 21:43 ` Christian Brauner
2026-01-06 21:43 ` Christian Brauner
2026-01-07 7:32 ` Christoph Hellwig
2026-01-07 7:32 ` Christoph Hellwig
2026-01-12 10:04 ` Christian Brauner
2026-01-12 10:04 ` Christian Brauner
2026-01-12 10:05 ` Christoph Hellwig
2026-01-12 10:05 ` Christoph Hellwig
2026-01-12 13:22 ` Christian Brauner
2026-01-12 13:22 ` Christian Brauner
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=202512291537.9abd5523-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=devel@lists.orangefs.org \
--cc=dsterba@suse.com \
--cc=gfs2@lists.linux.dev \
--cc=hch@lst.de \
--cc=hubcap@omnibond.com \
--cc=io-uring@vger.kernel.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=martin@omnibond.com \
--cc=oe-lkp@lists.linux.dev \
--cc=shr@fb.com \
--cc=viro@zeniv.linux.org.uk \
/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.