From: kernel test robot <oliver.sang@intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: Jan Kara <jack@suse.cz>,
lkp@intel.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, Aleksa Sarai <cyphar@cyphar.com>,
oliver.sang@intel.com, oe-lkp@lists.linux.dev,
ltp@lists.linux.it
Subject: [LTP] [linus:master] [pidfs] 3c17001b21: ltp.ioctl_pidfd05.fail
Date: Mon, 27 Oct 2025 14:18:41 +0800 [thread overview]
Message-ID: <202510271348.f0d33753-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "ltp.ioctl_pidfd05.fail" on:
commit: 3c17001b21b9f168c957ced9384abe969019b609 ("pidfs: validate extensible ioctls")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 566771afc7a81e343da9939f0bd848d3622e2501]
[test failed on linux-next/master 72fb0170ef1f45addf726319c52a0562b6913707]
in testcase: ltp
version: ltp-x86_64-8566228f2-1_20251019
with following parameters:
disk: 1HDD
fs: f2fs
test: syscalls-06/ioctl_pidfd05
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/202510271348.f0d33753-lkp@intel.com
Running tests.......
<<<test_start>>>
tag=ioctl_pidfd05 stime=1761396961
cmdline="ioctl_pidfd05"
contacts=""
analysis=exit
<<<test_output>>>
tst_buffers.c:57: TINFO: Test is using guarded buffers
tst_test.c:2021: TINFO: LTP version: 20250930-11-g8566228f2
tst_test.c:2024: TINFO: Tested kernel: 6.17.0-rc1-00001-g3c17001b21b9 #1 SMP PREEMPT_DYNAMIC Sat Oct 25 19:45:26 CST 2025 x86_64
tst_kconfig.c:88: TINFO: Parsing kernel config '/proc/config.gz'
tst_kconfig.c:676: TINFO: CONFIG_KASAN kernel option detected which might slow the execution
tst_test.c:1842: TINFO: Overall timeout per run is 0h 10m 00s
ioctl_pidfd05.c:45: TPASS: ioctl(pidfd, PIDFD_GET_INFO, NULL) : EINVAL (22)
ioctl_pidfd05.c:46: TFAIL: ioctl(pidfd, PIDFD_GET_INFO_SHORT, info_invalid) expected EINVAL: ENOTTY (25)
Summary:
passed 1
failed 1
broken 0
skipped 0
warnings 0
incrementing stop
<<<execution_status>>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=2
<<<test_end>>>
INFO: ltp-pan reported some tests FAIL
LTP Version: 20250930-11-g8566228f2
###############################################################
Done executing testcases.
LTP Version: 20250930-11-g8566228f2
###############################################################
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20251027/202510271348.f0d33753-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
--
Mailing list info: https://lists.linux.it/listinfo/ltp
reply other threads:[~2025-10-27 6:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202510271348.f0d33753-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=brauner@kernel.org \
--cc=cyphar@cyphar.com \
--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