From: Baochen Qiang <quic_bqiang@quicinc.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
Christoph Hellwig <hch@lst.de>
Cc: Robin Murphy <robin.murphy@arm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
<iommu@lists.linux.dev>
Subject: Re: missing clear bdr in check_ram_in_range_map()?
Date: Tue, 4 Mar 2025 09:59:10 +0800 [thread overview]
Message-ID: <83cec3f0-0c11-47bc-8a8d-517e2d0ead8c@quicinc.com> (raw)
In-Reply-To: <8045065f-723a-4b1f-bd89-23a1ab98ec7a@samsung.com>
On 2/28/2025 9:22 PM, Marek Szyprowski wrote:
> Hi,
>
> On 20.12.2024 04:25, Baochen Qiang wrote:
>> On 12/12/2024 3:14 PM, Christoph Hellwig wrote:
>>> On Mon, Dec 09, 2024 at 06:50:06PM +0800, Baochen Qiang wrote:
>>>> Hi,
>>>>
>>>> while checking check_ram_in_range_map() I am confused by the condition set/check on bdr.
>>>> If I am reading the code correctly, if bdr is set once, it would never get cleared, hence
>>>> that function will always returns 0.
>>>>
>>>> should we clear bdr before each new iteration?
>>> I think so. Even better refactor the code so that the non-NULL bdr
>>> doesn't leak out:
>>>
>>> diff --git a/kernel/dma/direct.c b/kernel/dma/direct.c
>>> index 5b4e6d3bf7bc..181e244f410a 100644
>>> --- a/kernel/dma/direct.c
>>> +++ b/kernel/dma/direct.c
>>> @@ -584,6 +584,22 @@ int dma_direct_supported(struct device *dev, u64 mask)
>>> return mask >= phys_to_dma_unencrypted(dev, min_mask);
>>> }
>>>
>>> +static const struct bus_dma_region *dma_find_range(struct device *dev,
>>> + unsigned long start_pfn)
>>> +{
>>> + const struct bus_dma_region *m;
>>> +
>>> + for (m = dev->dma_range_map; PFN_DOWN(m->size); m++) {
>>> + unsigned long cpu_start_pfn = PFN_DOWN(m->cpu_start);
>>> +
>>> + if (start_pfn >= cpu_start_pfn &&
>>> + start_pfn - cpu_start_pfn < PFN_DOWN(m->size))
>>> + return m;
>>> + }
>>> +
>>> + return NULL;
>>> +}
>>> +
>>> /*
>>> * To check whether all ram resource ranges are covered by dma range map
>>> * Returns 0 when further check is needed
>>> @@ -593,23 +609,14 @@ static int check_ram_in_range_map(unsigned long start_pfn,
>>> unsigned long nr_pages, void *data)
>>> {
>>> unsigned long end_pfn = start_pfn + nr_pages;
>>> - const struct bus_dma_region *bdr = NULL;
>>> - const struct bus_dma_region *m;
>>> struct device *dev = data;
>>>
>>> while (start_pfn < end_pfn) {
>>> - for (m = dev->dma_range_map; PFN_DOWN(m->size); m++) {
>>> - unsigned long cpu_start_pfn = PFN_DOWN(m->cpu_start);
>>> + const struct bus_dma_region *bdr;
>>>
>>> - if (start_pfn >= cpu_start_pfn &&
>>> - start_pfn - cpu_start_pfn < PFN_DOWN(m->size)) {
>>> - bdr = m;
>>> - break;
>>> - }
>>> - }
>>> + bdr = dma_find_range(dev, start_pfn);
>>> if (!bdr)
>>> return 1;
>>> -
>>> start_pfn = PFN_DOWN(bdr->cpu_start) + PFN_DOWN(bdr->size);
>>> }
>>>
>> looks better. thanks for reply.
>
> Could you send a formal patch with this fix, description and
> 'Suggested-by: Christoph Hellwig' tag?
sure, will submit soon.
>
> Best regards
prev parent reply other threads:[~2025-03-04 1:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 10:50 Baochen Qiang
2024-12-12 7:14 ` Christoph Hellwig
2024-12-20 3:25 ` Baochen Qiang
2025-02-28 13:22 ` Marek Szyprowski
2025-03-04 1:59 ` Baochen Qiang [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=83cec3f0-0c11-47bc-8a8d-517e2d0ead8c@quicinc.com \
--to=quic_bqiang@quicinc.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.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
all inboxes | Powered by JetHome®