From: Charan Teja Kalla <quic_charante@quicinc.com>
To: Robin Murphy <robin.murphy@arm.com>, Will Deacon <will@kernel.org>
Cc: <joro@8bytes.org>, <jgg@ziepe.ca>, <iommu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] iommu: fix wrong DMA ops for iommu device
Date: Wed, 22 Jan 2025 11:09:39 +0530 [thread overview]
Message-ID: <3caf4418-8ee2-4a61-b9ff-74b24155e436@quicinc.com> (raw)
In-Reply-To: <d1838296-0131-47ac-8a2e-eec8935c5960@quicinc.com>
On 1/20/2025 5:45 PM, Charan Teja Kalla wrote:
>> ----->8-----
>> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
>> index d1af0547f553..8d90d196e38d 100644
>> --- a/drivers/iommu/iommu.c
>> +++ b/drivers/iommu/iommu.c
>> @@ -3120,6 +3120,11 @@ int iommu_device_use_default_domain(struct device
>> *dev)
>> return 0;
>>
>> mutex_lock(&group->mutex);
>> + /* We may race against bus_iommu_probe() finalising groups here */
>> + if (!group->default_domain) {
>> + ret = -EPROBE_DEFER;
>> + goto unlock_out;
>> + }
> Please lmk If I can submit this as V2 patch, with your name as Suggested-by?
I missed to mention that this patch is fixing the problem we are
seeing..Thanks.
next prev parent reply other threads:[~2025-01-22 5:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 15:04 Charan Teja Kalla
2025-01-02 10:39 ` Charan Teja Kalla
2025-01-03 15:34 ` Will Deacon
2025-01-06 13:16 ` Charan Teja Kalla
2025-01-07 11:31 ` Will Deacon
2025-01-08 12:37 ` Robin Murphy
2025-01-10 13:29 ` Charan Teja Kalla
2025-01-13 17:25 ` Robin Murphy
2025-01-20 12:15 ` Charan Teja Kalla
2025-01-22 5:39 ` Charan Teja Kalla [this message]
2025-01-22 14:43 ` Robin Murphy
2025-01-24 0:32 ` Charan Teja Kalla
2025-01-24 14:17 ` Robin Murphy
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=3caf4418-8ee2-4a61-b9ff-74b24155e436@quicinc.com \
--to=quic_charante@quicinc.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--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®