patches.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Nicolin Chen <nicolinc@nvidia.com>
Cc: kevin.tian@intel.com, yi.l.liu@intel.com, iommu@lists.linux.dev,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	patches@lists.linux.dev
Subject: Re: [PATCH rc 0/3] iommufd: Fix three bugs found by Syzkaller
Date: Thu, 29 Feb 2024 11:59:06 -0400	[thread overview]
Message-ID: <20240229155906.GI9179@nvidia.com> (raw)
In-Reply-To: <cover.1708636627.git.nicolinc@nvidia.com>

On Thu, Feb 22, 2024 at 01:23:44PM -0800, Nicolin Chen wrote:
> Jason has been running Syzkaller that found three bugs.
> 
> Fix them properly.
> 
> Nicolin Chen (3):
>   iommufd: Fix iopt_access_list_id overwrite bug
>   iommufd/selftest: Fix mock_dev_num bug
>   iommufd: Fix protection fault in iommufd_test_syz_conv_iova
> 
>  drivers/iommu/iommufd/io_pagetable.c |  9 ++++---
>  drivers/iommu/iommufd/selftest.c     | 40 +++++++++++++++++++++-------
>  2 files changed, 36 insertions(+), 13 deletions(-)

Applied to for-rc

Thanks,
Jason 

      parent reply	other threads:[~2024-02-29 15:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 21:23 [PATCH rc 0/3] iommufd: Fix three bugs found by Syzkaller Nicolin Chen
2024-02-22 21:23 ` [PATCH rc 1/3] iommufd: Fix iopt_access_list_id overwrite bug Nicolin Chen
2024-02-22 21:23 ` [PATCH rc 2/3] iommufd/selftest: Fix mock_dev_num bug Nicolin Chen
2024-02-22 21:23 ` [PATCH rc 3/3] iommufd: Fix protection fault in iommufd_test_syz_conv_iova Nicolin Chen
2024-02-27  3:34 ` [PATCH rc 0/3] iommufd: Fix three bugs found by Syzkaller Tian, Kevin
2024-02-28 22:59   ` Jason Gunthorpe
2024-02-29 15:59 ` 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=20240229155906.GI9179@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=iommu@lists.linux.dev \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=patches@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).