From: kernel test robot <oliver.sang@intel.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, Joerg Roedel <jroedel@suse.de>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Christoph Hellwig <hch@lst.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
Jason Gunthorpe <jgg@nvidia.com>,
"Jerry Snitselaar" <jsnitsel@redhat.com>, <iommu@lists.linux.dev>,
<linux-acpi@vger.kernel.org>, <acpica-devel@lists.linux.dev>,
<oliver.sang@intel.com>
Subject: [linus:master] [iommu] 17de3f5fdd: kernel-selftests.iommu.iommufd_fail_nth.fail
Date: Mon, 30 Dec 2024 15:25:13 +0800 [thread overview]
Message-ID: <202412301525.87d1422b-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "kernel-selftests.iommu.iommufd_fail_nth.fail" on:
commit: 17de3f5fdd35676b0e3d41c7c9bf4e3032eb3673 ("iommu: Retire bus ops")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master fd0584d220fe285dc45be43eede55df89ad6a3d9]
[test failed on linux-next/master 8155b4ef3466f0e289e8fcc9e6e62f3f4dceeac2]
in testcase: kernel-selftests
version: kernel-selftests-x86_64-7503345ac5f5-1_20241208
with following parameters:
group: iommu
config: x86_64-dcg_x86_64_defconfig-kselftests
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/202412301525.87d1422b-lkp@intel.com
# timeout set to 300
# selftests: iommu: iommufd_fail_nth
# TAP version 13
# 1..7
# # Starting 7 tests from 1 test cases.
# # RUN basic_fail_nth.basic ...
# # OK basic_fail_nth.basic
# ok 1 basic_fail_nth.basic
# # RUN basic_fail_nth.map_domain ...
# # iommufd_fail_nth.c:299:map_domain:Expected 0 (0) == test_nth_map_domain(_metadata, self, variant, &nth_state) (-1)
# # map_domain: Test terminated by assertion
# # FAIL basic_fail_nth.map_domain
# not ok 2 basic_fail_nth.map_domain
# # RUN basic_fail_nth.map_two_domains ...
# # iommufd_fail_nth.c:334:map_two_domains:Expected 0 (0) == test_nth_map_two_domains(_metadata, self, variant, &nth_state) (-1)
# # map_two_domains: Test terminated by assertion
# # FAIL basic_fail_nth.map_two_domains
# not ok 3 basic_fail_nth.map_two_domains
# # RUN basic_fail_nth.access_rw ...
# # OK basic_fail_nth.access_rw
# ok 4 basic_fail_nth.access_rw
# # RUN basic_fail_nth.access_pin ...
# # OK basic_fail_nth.access_pin
# ok 5 basic_fail_nth.access_pin
# # RUN basic_fail_nth.access_pin_domain ...
# # iommufd_fail_nth.c:515:access_pin_domain:Expected 0 (0) == test_nth_access_pin_domain(_metadata, self, variant, &nth_state) (-1)
# # access_pin_domain: Test terminated by assertion
# # FAIL basic_fail_nth.access_pin_domain
# not ok 6 basic_fail_nth.access_pin_domain
# # RUN basic_fail_nth.device ...
# # iommufd_fail_nth.c:577:device:Expected 0 (0) == test_nth_device(_metadata, self, variant, &nth_state) (-1)
# # device: Test terminated by assertion
# # FAIL basic_fail_nth.device
# not ok 7 basic_fail_nth.device
# # FAILED: 3 / 7 tests passed.
# # Totals: pass:3 fail:4 xfail:0 xpass:0 skip:0 error:0
not ok 2 selftests: iommu: iommufd_fail_nth # exit=1
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20241230/202412301525.87d1422b-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-12-30 7:25 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=202412301525.87d1422b-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=acpica-devel@lists.linux.dev \
--cc=baolu.lu@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jroedel@suse.de \
--cc=jsnitsel@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=rafael.j.wysocki@intel.com \
--cc=robin.murphy@arm.com \
/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