From: Jason Gunthorpe <jgg@nvidia.com>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Joao Martins <joao.m.martins@oracle.com>,
Mirsad Todorovac <mirsad.todorovac@alu.unizg.hr>,
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, 2 Apr 2024 08:33:20 -0300 [thread overview]
Message-ID: <20240402113320.GO946323@nvidia.com> (raw)
In-Reply-To: <24c54707-421f-4c5b-8a34-245328cad347@linuxfoundation.org>
On Wed, Mar 27, 2024 at 06:05:46PM -0600, Shuah Khan wrote:
> ASSERT_*() is supposed to exit the test right away. If this
> isn't happening it needs to be debugged.
We know it doesn't work in setup/teardown functions, you can see it in
the code it jumps back and does the teardown again in an infinite
loop.
If mising assert and ASSERT causes loops that is also a bug, we can't
guarentee that no libraries linked into this (like glibc) doesn't call
assert.
Jason
next prev parent reply other threads:[~2024-04-02 11:33 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
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 [this message]
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=20240402113320.GO946323@nvidia.com \
--to=jgg@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=joao.m.martins@oracle.com \
--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 \
--cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.