From: Jason Gunthorpe <jgg@nvidia.com>
To: iommu@lists.linux.dev, Kevin Tian <kevin.tian@intel.com>,
linux-kselftest@vger.kernel.org
Cc: Lixiao Yang <lixiao.yang@intel.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Nicolin Chen <nicolinc@nvidia.com>,
Pengfei Xu <pengfei.xu@intel.com>, Yi Liu <yi.l.liu@intel.com>
Subject: Re: [PATCH 0/4] Fix three syzkaller splats in iommufd
Date: Tue, 4 Apr 2023 10:25:59 -0300 [thread overview]
Message-ID: <ZCwlZyRwGBleXeys@nvidia.com> (raw)
In-Reply-To: <0-v1-ceab6a4d7d7a+94-iommufd_syz_jgg@nvidia.com>
On Fri, Mar 31, 2023 at 12:32:23PM -0300, Jason Gunthorpe wrote:
> All related to the pages code, and the latter are reproducible with a
> simple test.
>
> Jason Gunthorpe (4):
> iommufd: Check for uptr overflow
> iommufd: Fix unpinning of pages when an access is present
> iommufd: Do not corrupt the pfn list when doing batch carry
> iommufd/selftest: Cover domain unmap with huge pages and access
>
> drivers/iommu/iommufd/pages.c | 16 ++++++++++--
> tools/testing/selftests/iommu/iommufd.c | 34 +++++++++++++++++++++++++
> 2 files changed, 48 insertions(+), 2 deletions(-)
I picked these up to go to -rc
Jason
prev parent reply other threads:[~2023-04-04 13:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 15:32 [PATCH 0/4] Fix three syzkaller splats in iommufd Jason Gunthorpe
2023-03-31 15:32 ` [PATCH 1/4] iommufd: Check for uptr overflow Jason Gunthorpe
2023-04-04 9:41 ` Tian, Kevin
2023-03-31 15:32 ` [PATCH 2/4] iommufd: Fix unpinning of pages when an access is present Jason Gunthorpe
2023-04-01 6:23 ` Pengfei Xu
2023-04-04 9:43 ` Tian, Kevin
2023-03-31 15:32 ` [PATCH 3/4] iommufd: Do not corrupt the pfn list when doing batch carry Jason Gunthorpe
2023-04-01 6:29 ` Pengfei Xu
2023-04-03 7:02 ` Pengfei Xu
2023-04-04 13:01 ` Jason Gunthorpe
2023-04-04 13:36 ` Pengfei Xu
2023-04-04 9:44 ` Tian, Kevin
2023-03-31 15:32 ` [PATCH 4/4] iommufd/selftest: Cover domain unmap with huge pages and access Jason Gunthorpe
2023-04-04 9:48 ` Tian, Kevin
2023-04-04 13:25 ` 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=ZCwlZyRwGBleXeys@nvidia.com \
--to=jgg@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=lixiao.yang@intel.com \
--cc=mjrosato@linux.ibm.com \
--cc=nicolinc@nvidia.com \
--cc=pengfei.xu@intel.com \
--cc=yi.l.liu@intel.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