From: Robin Murphy <robin.murphy@arm.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
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: Thu, 8 Feb 2024 01:37:52 +0000 [thread overview]
Message-ID: <a93e93dd-5cb8-48ee-bf8d-b3bbb19507d6@arm.com> (raw)
In-Reply-To: <20240208011305.GM31743@ziepe.ca>
On 2024-02-08 1:13 am, Jason Gunthorpe wrote:
> 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?
I mean you're literally getting bug reports for your fix for your fix
for your grand idea, so what should we figure, that reality not aligning
with your expectations is all reality's fault?
>> 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?
"at 12:04:44AM +0000, Robin Murphy wrote:"
It's late, I should have gone to bed hours ago, so I apologise for any
lack of clarity; that was very much meant to be an implication of
agreement with the overall approach, not the exact patch as is, which if
you read the rest of my response you will see I still had questions
about and did not formally ack or review.
> 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.
Hurrah! Please apply that kind of rigour to your own patches also.
Thanks,
Robin.
[ you get two responses this week since I admit I ran out of patience
and motivation to finish last week's on time ]
next prev parent reply other threads:[~2024-02-08 1:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 10:11 [PATCH 1/1] iommu: Avoid races around default domain allocations 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
2024-02-08 1:37 ` Robin Murphy [this message]
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=a93e93dd-5cb8-48ee-bf8d-b3bbb19507d6@arm.com \
--to=robin.murphy@arm.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_charante@quicinc.com \
--cc=quic_nprakash@quicinc.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