From: Jason Gunthorpe <jgg@nvidia.com>
To: Pranjal Shrivastava <praan@google.com>
Cc: Joerg Roedel <joro@8bytes.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
y@google.com, Mostafa Saleh <smostafa@google.com>,
iommu@lists.linux.dev, Kunkun Jiang <jiangkunkun@huawei.com>
Subject: Re: [PATCH] iommu: Handle iommu faults for a bad iopf setup
Date: Thu, 15 Aug 2024 10:00:52 -0300 [thread overview]
Message-ID: <20240815130052.GF2032816@nvidia.com> (raw)
In-Reply-To: <Zr36-J4fZ8PlcvV6@google.com>
On Thu, Aug 15, 2024 at 12:56:24PM +0000, Pranjal Shrivastava wrote:
> On Thu, Aug 15, 2024 at 09:46:11AM -0300, Jason Gunthorpe wrote:
> > On Thu, Aug 15, 2024 at 12:42:14PM +0000, Pranjal Shrivastava wrote:
> >
> > > > if (!(fault->prm.flags & IOMMU_FAULT_PAGE_REQUEST_LAST_PAGE)) {
> > > > report_partial_fault(iopf_param, fault);
> > >
> > > Apologies, I sent out an older version that missed returning a value.
> > > Please ignore this email, I'll resend the updated version.
> >
> > It is probably Ok, the merge should resolve it.
> >
> > The fix is already in linux-next:
> >
> > commit fca5b78511e98bdff2cdd55c172b23200a7b3404
> > Author: Barak Biber <bbiber@nvidia.com>
> > Date: Thu Aug 1 09:26:04 2024 -0300
> >
> > iommu: Restore lost return in iommu_report_device_fault()
> >
> > When iommu_report_device_fault gets called with a partial fault it is
> > supposed to collect the fault into the group and then return.
> >
> > Instead the return was accidently deleted which results in trying to
> > process the fault and an eventual crash.
> >
> > Deleting the return was a typo, put it back.
> >
> > Fixes: 3dfa64aecbaf ("iommu: Make iommu_report_device_fault() return void")
> > Signed-off-by: Barak Biber <bbiber@nvidia.com>
> > Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> > Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>
> > Link: https://lore.kernel.org/r/0-v1-e7153d9c8cee+1c6-iommu_fault_fix_jgg@nvidia.com
> > Signed-off-by: Joerg Roedel <jroedel@suse.de>
> >
> >
> > But doesn't look like it made it to rc3 yet
>
> I guess it's there on as it gave me a build error as the `return;`
> statement was returning void for a non-void function. Fixed this and
> sent it as a v2 of this patch.
Oh I see now, yes, that is the right thing to do!
You should also put [PATCH rc] so Joerg knows this is for rc as we are
fixing a regression in this merge window.
Jason
prev parent reply other threads:[~2024-08-15 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 12:32 [PATCH] iommu: Handle iommu faults for a bad iopf setup Pranjal Shrivastava
2024-08-15 12:42 ` Pranjal Shrivastava
2024-08-15 12:46 ` Jason Gunthorpe
2024-08-15 12:56 ` Pranjal Shrivastava
2024-08-15 13:00 ` 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=20240815130052.GF2032816@nvidia.com \
--to=jgg@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jiangkunkun@huawei.com \
--cc=joro@8bytes.org \
--cc=praan@google.com \
--cc=robin.murphy@arm.com \
--cc=smostafa@google.com \
--cc=will@kernel.org \
--cc=y@google.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