From: Jason Gunthorpe <jgg@ziepe.ca>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Nikhil V <quic_nprakash@quicinc.com>,
Will Deacon <will@kernel.org>, Joerg Roedel <joro@8bytes.org>,
Charan Teja Kalla <quic_charante@quicinc.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] iommu: Avoid races around default domain allocations
Date: Wed, 7 Feb 2024 21:13:05 -0400 [thread overview]
Message-ID: <20240208011305.GM31743@ziepe.ca> (raw)
In-Reply-To: <37ab8689-5e0d-4166-bad6-84d3c51446ca@arm.com>
On Thu, Feb 08, 2024 at 12:04:44AM +0000, Robin Murphy wrote:
> > Frankly, I'd suggest just proposing the necessary (and tested)
> > upstream patches to 6.1, however large they are, and see what Greg and
> > Sasha say. This is the usual working model they have, as I understand
> > it.
>
> To be blunt, hell no. Stable is far enough from its namesake already; the
> ongoing bordering-on-ridiculous brokenness of your mainline changes where
What on earth are you even talking about? POWER?
> That said, I also don't think there would be any harm in applying this to
> mainline as a belt-and-braces thing either,
Really?
Now that you've made me look, this patch breaks the
iommu_group_store_type() flow both on latest and on v6.1 from what I
can see.
On v6.1:
iommu_change_dev_def_domain():
prev_dom = group->default_domain;
if (!prev_dom) {
ret = -EINVAL;
goto out;
}
[..]
/* Sets group->default_domain to the newly allocated domain */
ret = iommu_group_alloc_default_domain(dev->bus, group, type);
if (ret)
goto out;
But this patch changes iommu_group_alloc_default_domain() to succeed
always without doing anythiing.
So this patch needs some fixing.
There is a very good reason the stable people don't like boutique patches..
Jason
next prev parent reply other threads:[~2024-02-08 1:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 10:11 Nikhil V
2024-01-29 7:59 ` Nikhil V
2024-02-01 16:23 ` Jason Gunthorpe
2024-02-07 14:26 ` Nikhil V
2024-02-07 14:56 ` Jason Gunthorpe
2024-02-08 0:04 ` Robin Murphy
2024-02-08 1:13 ` Jason Gunthorpe [this message]
2024-02-08 1:37 ` Robin Murphy
2024-02-08 15:17 ` Nikhil V
2024-02-08 16:09 ` 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=20240208011305.GM31743@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_charante@quicinc.com \
--cc=quic_nprakash@quicinc.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
/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
all inboxes | Powered by JetHome®