From: kernel test robot <oliver.sang@intel.com>
To: Alyssa Ross <hi@alyssa.is>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>, <linux-mm@kvack.org>,
<linux-fsdevel@vger.kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
Kees Cook <keescook@chromium.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Eric Biederman <ebiederm@xmission.com>,
<linux-kernel@vger.kernel.org>, <oliver.sang@intel.com>
Subject: Re: [PATCH] exec: allow executing block devices
Date: Fri, 20 Oct 2023 14:06:31 +0800 [thread overview]
Message-ID: <202310201132.ec34d76b-oliver.sang@intel.com> (raw)
In-Reply-To: <20231010092133.4093612-1-hi@alyssa.is>
Hello,
kernel test robot noticed "kernel-selftests.exec.non-regular.fail" on:
commit: f086dcc88a64a2022314af666bd15d64c6748d27 ("[PATCH] exec: allow executing block devices")
url: https://github.com/intel-lab-lkp/linux/commits/Alyssa-Ross/exec-allow-executing-block-devices/20231010-172704
patch link: https://lore.kernel.org/all/20231010092133.4093612-1-hi@alyssa.is/
patch subject: [PATCH] exec: allow executing block devices
in testcase: kernel-selftests
version: kernel-selftests-x86_64-60acb023-1_20230329
with following parameters:
group: group-01
compiler: gcc-12
test machine: 36 threads 1 sockets Intel(R) Core(TM) i9-10980XE CPU @ 3.00GHz (Cascade Lake) with 32G 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/202310201132.ec34d76b-oliver.sang@intel.com
# timeout set to 300
# selftests: exec: non-regular
# TAP version 13
# 1..6
# # Starting 6 tests from 6 test cases.
# # RUN file.S_IFLNK.exec_errno ...
# # OK file.S_IFLNK.exec_errno
# ok 1 file.S_IFLNK.exec_errno
# # RUN file.S_IFDIR.exec_errno ...
# # OK file.S_IFDIR.exec_errno
# ok 2 file.S_IFDIR.exec_errno
# # RUN file.S_IFBLK.exec_errno ...
# # non-regular.c:166:exec_errno:Expected errno (6) == variant->expected (13)
# # exec_errno: Test failed at step #4
# # FAIL file.S_IFBLK.exec_errno
# not ok 3 file.S_IFBLK.exec_errno
# # RUN file.S_IFCHR.exec_errno ...
# # OK file.S_IFCHR.exec_errno
# ok 4 file.S_IFCHR.exec_errno
# # RUN file.S_IFIFO.exec_errno ...
# # OK file.S_IFIFO.exec_errno
# ok 5 file.S_IFIFO.exec_errno
# # RUN sock.exec_errno ...
# # OK sock.exec_errno
# ok 6 sock.exec_errno
# # FAILED: 5 / 6 tests passed.
# # Totals: pass:5 fail:1 xfail:0 xpass:0 skip:0 error:0
not ok 5 selftests: exec: non-regular # exit=1
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20231020/202310201132.ec34d76b-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2023-10-20 6:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20231010092133.4093612-1-hi@alyssa.is>]
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=202310201132.ec34d76b-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=hi@alyssa.is \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=viro@zeniv.linux.org.uk \
/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).