From: kernel test robot <oliver.sang@intel.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Christian Brauner <brauner@kernel.org>,
Christoph Hellwig <hch@lst.de>, Jan Kara <jack@suse.cz>,
<linux-ext4@vger.kernel.org>, <ltp@lists.linux.it>,
<oliver.sang@intel.com>
Subject: [linux-next:master] [ext4] 81d2e13a57: ltp.fanotify22.fail
Date: Wed, 4 Feb 2026 22:10:10 +0800 [thread overview]
Message-ID: <202602042124.87bd00e3-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "ltp.fanotify22.fail" on:
commit: 81d2e13a57c9d73582527966fae24d4fd73826ca ("ext4: convert to new fserror helpers")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 33a647c659ffa5bdb94abc345c8c86768ff96215]
in testcase: ltp
version:
with following parameters:
disk: 1HDD
fs: btrfs
test: syscalls-02/fanotify22
config: x86_64-rhel-9.4-ltp
compiler: gcc-14
test machine: 4 threads 1 sockets Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz (Ivy Bridge) with 8G 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/202602042124.87bd00e3-lkp@intel.com
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260204/202602042124.87bd00e3-lkp@intel.com
user :notice: [ 423.546026] [ T265] Hostname: lkp-ivb-d04
user :notice: [ 423.554417] [ T265] Python: 3.13.5 (main, Jun 25 2025, 18:55:22) [GCC 14.2.0]
user :notice: [ 423.570800] [ T265] Directory: /tmp/kirk.root/tmpefuyb6o0
user :notice: [ 423.584852] [ T265] Connecting to SUT: default
user :warn : [ 423.586640] [ T5587] /lkp/benchmarks/ltp/kirk[5563]: fanotify22: start (command: fanotify22)
user :notice: [ 423.605665] [ T265] Starting suite: temp_single_test
user :notice: [ 423.613894] [ T265] ---------------------------------
kern :info : [ 423.633832] [ T5592] loop: module loaded
kern :info : [ 423.657047] [ T5591] loop0: detected capacity change from 0 to 614400
kern :err : [ 423.821741] [ T5591] /dev/zero: Can't lookup blockdev
kern :info : [ 424.033575] [ T5591] EXT4-fs (loop0): mounted filesystem 6b5acef8-3cdb-48f2-8af0-b27b5ee321e9 r/w with ordered data mode. Quota mode: none.
kern :info : [ 424.098309] [ T5607] EXT4-fs (loop0): unmounting filesystem 6b5acef8-3cdb-48f2-8af0-b27b5ee321e9.
kern :info : [ 424.345598] [ T5607] EXT4-fs (loop0): mounted filesystem 6b5acef8-3cdb-48f2-8af0-b27b5ee321e9 r/w with ordered data mode. Quota mode: none.
kern :crit : [ 424.414068] [ T5607] EXT4-fs error (device loop0): __ext4_remount:6794: comm fanotify22: Abort forced by user
kern :err : [ 424.423984] [ T5607] Aborting journal on device loop0-8.
kern :crit : [ 424.463989] [ T5607] EXT4-fs (loop0): Remounting filesystem read-only
kern :info : [ 424.470416] [ T5607] EXT4-fs (loop0): re-mounted 6b5acef8-3cdb-48f2-8af0-b27b5ee321e9 ro.
kern :info : [ 424.479591] [ T5607] EXT4-fs (loop0): unmounting filesystem 6b5acef8-3cdb-48f2-8af0-b27b5ee321e9.
kern :warn : [ 424.490528] [ T5607] EXT4-fs (loop0): warning: mounting fs with errors, running e2fsck is recommended
kern :info : [ 424.539426] [ T5607] EXT4-fs (loop0): mounted filesystem 6b5acef8-3cdb-48f2-8af0-b27b5ee321e9 r/w with ordered data mode. Quota mode: none.
kern :crit : [ 424.552662] [ T5607] EXT4-fs error (device loop0): ext4_lookup:1785: inode #32386: comm fanotify22: iget: bogus i_mode (377)
kern :info : [ 424.617262] [ T5607] EXT4-fs (loop0): unmounting filesystem 6b5acef8-3cdb-48f2-8af0-b27b5ee321e9.
kern :warn : [ 424.703481] [ T5607] EXT4-fs (loop0): warning: mounting fs with errors, running e2fsck is recommended
kern :info : [ 424.752431] [ T5607] EXT4-fs (loop0): mounted filesystem 6b5acef8-3cdb-48f2-8af0-b27b5ee321e9 r/w with ordered data mode. Quota mode: none.
kern :crit : [ 424.765440] [ T5607] EXT4-fs error (device loop0): ext4_lookup:1777: inode #32385: comm fanotify22: bad inode number: 1
kern :crit : [ 424.776331] [ T5607] EXT4-fs error (device loop0): ext4_lookup:1785: inode #32386: comm fanotify22: iget: bogus i_mode (377)
kern :info : [ 424.845037] [ T5607] EXT4-fs (loop0): unmounting filesystem 6b5acef8-3cdb-48f2-8af0-b27b5ee321e9.
kern :warn : [ 424.928434] [ T5607] EXT4-fs (loop0): warning: mounting fs with errors, running e2fsck is recommended
kern :info : [ 424.985535] [ T5607] EXT4-fs (loop0): mounted filesystem 6b5acef8-3cdb-48f2-8af0-b27b5ee321e9 r/w with ordered data mode. Quota mode: none.
kern :crit : [ 424.998543] [ T5607] EXT4-fs error (device loop0): ext4_lookup:1785: inode #32386: comm fanotify22: iget: bogus i_mode (377)
kern :crit : [ 425.115411] [ T5607] EXT4-fs error (device loop0): __ext4_remount:6794: comm fanotify22: Abort forced by user
kern :err : [ 425.125337] [ T5607] Aborting journal on device loop0-8.
kern :crit : [ 425.191808] [ T5607] EXT4-fs (loop0): Remounting filesystem read-only
kern :info : [ 425.198225] [ T5607] EXT4-fs (loop0): re-mounted 6b5acef8-3cdb-48f2-8af0-b27b5ee321e9 ro.
kern :info : [ 425.207311] [ T5607] EXT4-fs (loop0): unmounting filesystem 6b5acef8-3cdb-48f2-8af0-b27b5ee321e9.
kern :warn : [ 425.218247] [ T5607] EXT4-fs (loop0): warning: mounting fs with errors, running e2fsck is recommended
kern :info : [ 425.255422] [ T5607] EXT4-fs (loop0): mounted filesystem 6b5acef8-3cdb-48f2-8af0-b27b5ee321e9 r/w with ordered data mode. Quota mode: none.
kern :info : [ 425.300422] [ T5591] EXT4-fs (loop0): unmounting filesystem 6b5acef8-3cdb-48f2-8af0-b27b5ee321e9.
user :notice: [ 425.421952] [ T265] \x1b[1;37mfanotify22: \x1b[0m\x1b[1;31mfail\x1b[0m | \x1b[1;33mtainted\x1b[0m (1.808s)
user :warn : [ 425.427743] [ T5635] /lkp/benchmarks/ltp/kirk[5563]: fanotify22: end (returncode: 1)
user :notice: [ 425.447575] [ T265]
user :notice: [ 425.463971] [ T265] Execution time: 1.866s
user :notice: [ 425.476018] [ T265] Suite: temp_single_test
user :notice: [ 425.483786] [ T265] Total runs: 1
user :notice: [ 425.490690] [ T265] Runtime: 1.808s
user :notice: [ 425.497330] [ T265] Passed: 3
user :notice: [ 425.503518] [ T265] Failed: 1
user :notice: [ 425.509637] [ T265] Skipped: 0
user :notice: [ 425.515735] [ T265] Broken: 0
user :notice: [ 425.521820] [ T265] Warnings: 0
user :notice: [ 425.529960] [ T265] Kernel: Linux 6.19.0-rc1-00006-g81d2e13a57c9 #1 SMP PREEMPT_DYNAMIC Sat Jan 31 20:49:54 CST 2026
user :notice: [ 425.543805] [ T265] Machine: unknown
user :notice: [ 425.550576] [ T265] Arch: x86_64
user :notice: [ 425.557336] [ T265] RAM: 6899604 kB
user :notice: [ 425.564451] [ T265] Swap: 0 kB
user :notice: [ 425.571112] [ T265] Distro: debian 13
user :notice: [ 425.582858] [ T265] Disconnecting from SUT: default
user :notice: [ 425.590377] [ T265] Session stopped
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-02-04 14:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 14:10 kernel test robot [this message]
2026-03-06 12:19 ` [LTP] [linux-next:master] [ext4] 81d2e13a57: ltp.fanotify22.fail Petr Vorel
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=202602042124.87bd00e3-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ltp@lists.linux.it \
--cc=oe-lkp@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