From: Jason Gunthorpe <jgg@nvidia.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: Nicolin Chen <nicolinc@nvidia.com>,
"Liu, Yi L" <yi.l.liu@intel.com>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"patches@lists.linux.dev" <patches@lists.linux.dev>
Subject: Re: [PATCH rc 0/3] iommufd: Fix three bugs found by Syzkaller
Date: Wed, 28 Feb 2024 18:59:29 -0400 [thread overview]
Message-ID: <20240228225929.GR13330@nvidia.com> (raw)
In-Reply-To: <BN9PR11MB5276D622986E55465C3977CB8C592@BN9PR11MB5276.namprd11.prod.outlook.com>
On Tue, Feb 27, 2024 at 03:34:11AM +0000, Tian, Kevin wrote:
> > From: Nicolin Chen <nicolinc@nvidia.com>
> > Sent: Friday, February 23, 2024 5:24 AM
> >
> > Jason has been running Syzkaller that found three bugs.
>
> could you remove "Jason has been running" from all three patches?
> Just say that Syzkaller found a bug.
I will copy edit the commit messages
Thanks,
Jason
next prev parent reply other threads:[~2024-02-28 22: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 [this message]
2024-02-29 15:59 ` Jason Gunthorpe
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=20240228225929.GR13330@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).