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>,
Josef Bacik <josef@toxicpanda.com>, <linux-mm@kvack.org>,
<ltp@lists.linux.it>, <oliver.sang@intel.com>
Subject: [linus:master] [fs] 2a010c4128: ltp.execve04.fail
Date: Tue, 16 Jul 2024 21:22:59 +0800 [thread overview]
Message-ID: <202407162117.7730986d-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "ltp.execve04.fail" on:
commit: 2a010c41285345da60cece35575b4e0af7e7bf44 ("fs: don't block i_writecount during exec")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master d67978318827d06f1c0fa4c31343a279e9df6fde]
[test failed on linux-next/master 4f40be61af99a67d5580c1448acd9b74c0376389]
in testcase: ltp
version: ltp-x86_64-14c1f76-1_20240706
with following parameters:
disk: 1HDD
fs: f2fs
test: syscalls-05/execve04
compiler: gcc-13
test machine: 36 threads 1 sockets Intel(R) Core(TM) i9-10980XE CPU @ 3.00GHz (Cascade Lake) with 128G 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/202407162117.7730986d-oliver.sang@intel.com
Running tests.......
<<<test_start>>>
tag=execve04 stime=1721093644
cmdline="execve04"
contacts=""
analysis=exit
<<<test_output>>>
tst_test.c:1803: TINFO: LTP version: 20240524-71-g361f6ad13
tst_test.c:1647: TINFO: Timeout per run is 0h 02m 30s
execve_child.c:27: TFAIL: execve_child shouldn't be executed
tst_test.c:1695: TINFO: Killed the leftover descendant processes
Summary:
passed 0
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=6
<<<test_end>>>
INFO: ltp-pan reported some tests FAIL
LTP Version: 20240524-71-g361f6ad13
###############################################################
Done executing testcases.
LTP Version: 20240524-71-g361f6ad13
###############################################################
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240716/202407162117.7730986d-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-07-16 13:23 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=202407162117.7730986d-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=brauner@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).