From: Jason Gunthorpe <jgg@nvidia.com>
To: Mirsad Todorovac <mirsad.todorovac@alu.unizg.hr>
Cc: iommu@lists.linux.dev, Kevin Tian <kevin.tian@intel.com>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] seltests/iommu: runaway ./iommufd consuming 99% CPU after a failed assert()
Date: Tue, 19 Mar 2024 10:58:52 -0300 [thread overview]
Message-ID: <20240319135852.GA393211@nvidia.com> (raw)
In-Reply-To: <0d5c3b29-fc5b-41d9-9556-5ce94262dac8@alu.unizg.hr>
On Tue, Mar 12, 2024 at 07:35:40AM +0100, Mirsad Todorovac wrote:
> Hi,
>
> (This is verified on the second test box.)
>
> In the most recent 6.8.0 release of torvalds tree kernel with selftest configs on,
> process ./iommufd appears to consume 99% of a CPU core for quote a while in an
> endless loop:
There is a "bug" in the ksefltest framework where if you call a
kselftest assertion from the setup/teardown it infinite loops
The fix I know is to replace kselftest assertions with normal assert()
But I don't see an obvious thing here saying you are hitting that..
Jason
next prev parent reply other threads:[~2024-03-19 13:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 6:35 [BUG] seltests/iommu: runaway ./iommufd consuming 99% CPU after a failed assert() Mirsad Todorovac
2024-03-19 13:58 ` Jason Gunthorpe [this message]
2024-03-23 20:13 ` Mirsad Todorovac
2024-03-25 12:17 ` Joao Martins
2024-03-25 13:52 ` Jason Gunthorpe
2024-03-27 10:41 ` Joao Martins
2024-03-27 11:40 ` Jason Gunthorpe
2024-03-27 15:04 ` Joao Martins
2024-03-27 16:38 ` Jason Gunthorpe
2024-03-28 0:05 ` Shuah Khan
2024-04-02 11:33 ` Jason Gunthorpe
2024-03-27 20:04 ` Mirsad Todorovac
2024-03-28 13:54 ` Joao Martins
2024-04-04 16:54 ` Shuah Khan
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=20240319135852.GA393211@nvidia.com \
--to=jgg@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mirsad.todorovac@alu.unizg.hr \
--cc=shuah@kernel.org \
/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