From: kernel test robot <oliver.sang@intel.com>
To: AnonymeMeow <anonymemeow@gmail.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, Jan Kara <jack@suse.cz>,
Christian Brauner <brauner@kernel.org>,
<linux-fsdevel@vger.kernel.org>, <ltp@lists.linux.it>,
<oliver.sang@intel.com>
Subject: [linus:master] [fanotify] 82c6dd2047: ltp.fanotify21.fail
Date: Mon, 29 Jun 2026 16:45:58 +0800 [thread overview]
Message-ID: <202606291514.594c4370-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "ltp.fanotify21.fail" on:
commit: 82c6dd20479bb6a9625e1d63a650c3be8865e2db ("fanotify: allow reporting pidfds for reaped tasks")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 5a66900afbd6b2a063eebad35294038a654de2b0]
[test failed on linux-next/master 3d5670d672ae08b8c534b7beed6f57c8b44e7b43]
in testcase: ltp
version:
with following parameters:
disk: 1HDD
fs: xfs
test: syscalls-00
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/202606291514.594c4370-lkp@intel.com
^[[1;37mfanotify15: ^[[0m^[[1;36mskip^[[0m | ^[[1;33mtainted^[[0m (12.585s)
^[[1;37mfanotify21: ^[[0m^[[1;31mfail^[[0m | ^[[1;33mtainted^[[0m (25.438s) <------
^[[1;37mioprio_set02: ^[[0m^[[1;32mpass^[[0m | ^[[1;33mtainted^[[0m (0.037s)
...
Execution time: 9m 29s
Disconnecting from SUT: default
Target information
──────────────────
Kernel: Linux 7.1.0-rc3+ #1 SMP PREEMPT_DYNAMIC Fri Jun 26 20:05:34 CST 2026
Cmdline: ip=::::lkp-ivb-d04::dhcp
root=/dev/ram0
RESULT_ROOT=/result/ltp/1HDD-xfs-syscalls-00/lkp-ivb-d04/debian-13-x86_64-20250902.cgz/x86_64-rhel-9.4-ltp/gcc-14/82c6dd20479bb6a9625e1d63a650c3be8865e2db/0
BOOT_IMAGE=/pkg/linux/x86_64-rhel-9.4-ltp/gcc-14/82c6dd20479bb6a9625e1d63a650c3be8865e2db/vmlinuz-7.1.0-rc3+
branch=linux-next/master
job=/lkp/jobs/scheduled/lkp-ivb-d04/ltp-1HDD-xfs-syscalls-00-debian-13-x86_64-20250902.cgz-82c6dd20479b-20260626-11320-p5g804-0.yaml
user=lkp
ARCH=x86_64
kconfig=x86_64-rhel-9.4-ltp
commit=82c6dd20479bb6a9625e1d63a650c3be8865e2db
intremap=posted_msi
max_uptime=7200
LKP_SERVER=internal-lkp-server
nokaslr
selinux=0
debug
apic=debug
sysrq_always_enabled
rcupdate.rcu_cpu_stall_timeout=100
net.ifnames=0
printk.devkmsg=on
panic=-1
softlockup_panic=1
nmi_watchdog=panic
oops=panic
load_ramdisk=2
prompt_ramdisk=0
drbd.minor_count=8
systemd.log_level=err
ignore_loglevel
console=tty0
earlyprintk=ttyS0,115200
console=ttyS0,115200
vga=normal
rw
keep_initrds=/osimage/pkg/debian-13-x86_64-20250902.cgz/ltp-x86_64-5ccf816f5-1_20260531.cgz
Machine: unknown
Arch: x86_64
RAM: 6898364 kB
Swap: 0 kB
Distro: debian 13
────────────────────────
TEST SUMMARY
────────────────────────
Suite: syscalls-00
Runtime: 9m 15s
Runs: 188
Results:
Passed: 2339
Failed: 18
Broken: 0
Skipped: 45
Warnings: 0
^[[1;31mFailures:^[[0m
• fanotify21
Session stopped
/tmp/kirk.root/latest is not found
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260629/202606291514.594c4370-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-06-29 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 8:45 kernel test robot [this message]
2026-06-29 9:36 ` [linus:master] [fanotify] 82c6dd2047: ltp.fanotify21.fail Jan Kara
2026-06-30 5:18 ` Oliver Sang
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=202606291514.594c4370-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=anonymemeow@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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