From: Jason Gunthorpe <jgg@nvidia.com>
To: Nicolin Chen <nicolinc@nvidia.com>
Cc: kevin.tian@intel.com, shuah@kernel.org,
joao.m.martins@oracle.com, steven.sistare@oracle.com,
iommu@lists.linux.dev, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, thomas.weissschuh@linutronix.de
Subject: Re: [PATCH rc v2 0/4] Fix iommufd selftest FAIL and warnings with v6.16
Date: Thu, 26 Jun 2025 12:04:34 -0300 [thread overview]
Message-ID: <20250626150434.GM167785@nvidia.com> (raw)
In-Reply-To: <cover.1750787928.git.nicolinc@nvidia.com>
On Tue, Jun 24, 2025 at 11:00:44AM -0700, Nicolin Chen wrote:
> A few selftest harness changes being merged to v6.16, which exposed some
> bugs and vulnerabilities in the iommufd selftest code. Fix them properly.
>
> Note that the patch fixing the build warnings at mfd is not ideal, as it
> has possibly hit some corner case in the gcc:
> https://lore.kernel.org/all/aEi8DV+ReF3v3Rlf@nvidia.com/
>
> This is on github:
> https://github.com/nicolinc/iommufd/commits/iommufd_selftest_fixes-v6.16
>
> Changelog:
> v2
> * Add "Reviewed-by" from Jason
> * Only use kfree() in the teardown()
> * Add an mmap_buffer_size for readability
> v1
> https://lore.kernel.org/all/cover.1750049883.git.nicolinc@nvidia.com/
>
> Thanks
> Nicolin
>
> Nicolin Chen (4):
> iommufd/selftest: Fix iommufd_dirty_tracking with large hugepage sizes
> iommufd/selftest: Add missing close(mfd) in memfd_mmap()
> iommufd/selftest: Add asserts testing global mfd
> iommufd/selftest: Fix build warnings due to uninitialized mfd
Applied to for-rc, thanks
Jason
prev parent reply other threads:[~2025-06-26 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 18:00 [PATCH rc v2 0/4] Fix iommufd selftest FAIL and warnings with v6.16 Nicolin Chen
2025-06-24 18:00 ` [PATCH rc v2 1/4] iommufd/selftest: Fix iommufd_dirty_tracking with large hugepage sizes Nicolin Chen
2025-06-24 18:00 ` [PATCH rc v2 2/4] iommufd/selftest: Add missing close(mfd) in memfd_mmap() Nicolin Chen
2025-06-24 18:00 ` [PATCH rc v2 3/4] iommufd/selftest: Add asserts testing global mfd Nicolin Chen
2025-06-24 18:00 ` [PATCH rc v2 4/4] iommufd/selftest: Fix build warnings due to uninitialized mfd Nicolin Chen
2025-06-26 15:04 ` Jason Gunthorpe [this message]
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=20250626150434.GM167785@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=nicolinc@nvidia.com \
--cc=shuah@kernel.org \
--cc=steven.sistare@oracle.com \
--cc=thomas.weissschuh@linutronix.de \
/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.