From: kernel test robot <oliver.sang@intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<ltp@lists.linux.it>, <oliver.sang@intel.com>
Subject: [linus:master] [pidfd] cb12fd8e0d: ltp.readahead01.fail
Date: Fri, 15 Mar 2024 16:16:33 +0800 [thread overview]
Message-ID: <202403151507.5540b773-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "ltp.readahead01.fail" on:
commit: cb12fd8e0dabb9a1c8aef55a6a41e2c255fcdf4b ("pidfd: add pidfs")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 65d287c7eb1d14e0f4d56f19cec30d97fc7e8f66]
[test failed on linux-next/master a1184cae56bcb96b86df3ee0377cec507a3f56e0]
in testcase: ltp
version: ltp-x86_64-14c1f76-1_20240309
with following parameters:
disk: 1HDD
fs: f2fs
test: syscalls-00/readahead01
compiler: gcc-12
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/202403151507.5540b773-oliver.sang@intel.com
Running tests.......
<<<test_start>>>
tag=readahead01 stime=1710262698
cmdline="readahead01"
contacts=""
analysis=exit
<<<test_output>>>
tst_test.c:1741: TINFO: LTP version: 20240129-91-gcbc2d0568
tst_test.c:1625: TINFO: Timeout per run is 0h 02m 30s
readahead01.c:36: TPASS: readahead() with fd = -1 : EBADF (9)
readahead01.c:43: TPASS: readahead() with invalid fd : EBADF (9)
readahead01.c:63: TPASS: readahead() on O_PATH file : EBADF (9)
readahead01.c:63: TPASS: readahead() on directory : EINVAL (22)
readahead01.c:63: TPASS: readahead() on /dev/zero : EINVAL (22)
readahead01.c:63: TPASS: readahead() on pipe read end : EINVAL (22)
readahead01.c:63: TPASS: readahead() on pipe write end : EBADF (9)
readahead01.c:63: TPASS: readahead() on unix socket : EINVAL (22)
readahead01.c:63: TPASS: readahead() on inet socket : EINVAL (22)
readahead01.c:63: TPASS: readahead() on epoll : EINVAL (22)
readahead01.c:63: TPASS: readahead() on eventfd : EINVAL (22)
readahead01.c:63: TPASS: readahead() on signalfd : EINVAL (22)
readahead01.c:63: TPASS: readahead() on timerfd : EINVAL (22)
readahead01.c:63: TFAIL: readahead() on pidfd succeeded
readahead01.c:63: TPASS: readahead() on fanotify : EINVAL (22)
readahead01.c:63: TPASS: readahead() on inotify : EINVAL (22)
readahead01.c:63: TPASS: readahead() on userfaultfd : EINVAL (22)
readahead01.c:63: TPASS: readahead() on perf event : EINVAL (22)
readahead01.c:63: TPASS: readahead() on io uring : EINVAL (22)
readahead01.c:63: TPASS: readahead() on bpf map : EINVAL (22)
readahead01.c:63: TPASS: readahead() on fsopen : EINVAL (22)
readahead01.c:63: TPASS: readahead() on fspick : EINVAL (22)
readahead01.c:63: TPASS: readahead() on open_tree : EBADF (9)
Summary:
passed 22
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=3
<<<test_end>>>
INFO: ltp-pan reported some tests FAIL
LTP Version: 20240129-91-gcbc2d0568
###############################################################
Done executing testcases.
LTP Version: 20240129-91-gcbc2d0568
###############################################################
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240315/202403151507.5540b773-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-03-15 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 8:16 kernel test robot [this message]
2024-03-15 13:42 ` [linus:master] [pidfd] cb12fd8e0d: ltp.readahead01.fail Christian Brauner
2024-03-15 14:49 ` [LTP] " Cyril Hrubis
2024-03-18 8:47 ` Christian Brauner
2024-04-23 13:52 ` 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=202403151507.5540b773-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=brauner@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).