From: Jason Gunthorpe <jgg@nvidia.com>
To: iommu@lists.linux.dev
Cc: Alex Williamson <alex.williamson@redhat.com>,
Lu Baolu <baolu.lu@linux.intel.com>,
Eric Auger <eric.auger@redhat.com>,
Kevin Tian <kevin.tian@intel.com>,
Lixiao Yang <lixiao.yang@intel.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Nicolin Chen <nicolinc@nvidia.com>,
syzbot+7574ebfe589049630608@syzkaller.appspotmail.com,
Terrence Xu <terrence.xu@intel.com>, Yi Liu <yi.l.liu@intel.com>
Subject: Re: [PATCH rc 0/3] Several iommufd bug fixes
Date: Thu, 27 Jul 2023 11:31:59 -0300 [thread overview]
Message-ID: <ZMJ/3yN709dGq2GO@nvidia.com> (raw)
In-Reply-To: <0-v1-85aacb2af554+bc-iommufd_syz3_jgg@nvidia.com>
On Tue, Jul 25, 2023 at 04:05:47PM -0300, Jason Gunthorpe wrote:
> Syzkaller found another small issue, a race with
> iommufd_object_destroy_user() and IOMMUFD_DESTROY.
>
> While researching that I noticed an error unwind mistake by inspection.
>
> Yi and Nicolin stumbled on the last one running the test suite sometimes.
>
> Jason Gunthorpe (3):
> iommufd: IOMMUFD_DESTROY should not increase the refcount
> iommufd: Set end correctly when doing batch carry
I applied these to for-rc, thanks
Jason
prev parent reply other threads:[~2023-07-27 14:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 19:05 [PATCH rc 0/3] Several iommufd bug fixes Jason Gunthorpe
2023-07-25 19:05 ` [PATCH rc 1/3] iommufd/selftest: Do not try to destroy an access once it is attached Jason Gunthorpe
2023-07-25 21:45 ` Nicolin Chen
2023-07-26 16:40 ` Jason Gunthorpe
2023-07-26 3:53 ` Greg KH
2023-07-25 19:05 ` [PATCH rc 2/3] iommufd: IOMMUFD_DESTROY should not increase the refcount Jason Gunthorpe
2023-07-27 5:25 ` Tian, Kevin
2023-07-27 14:10 ` Jason Gunthorpe
2023-07-25 19:05 ` [PATCH rc 3/3] iommufd: Set end correctly when doing batch carry Jason Gunthorpe
2023-07-25 19:55 ` Nicolin Chen
2023-07-27 5:26 ` Tian, Kevin
2023-07-27 14:31 ` 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=ZMJ/3yN709dGq2GO@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=baolu.lu@linux.intel.com \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=lixiao.yang@intel.com \
--cc=mjrosato@linux.ibm.com \
--cc=nicolinc@nvidia.com \
--cc=syzbot+7574ebfe589049630608@syzkaller.appspotmail.com \
--cc=terrence.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 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.