From: Robin Murphy <robin.murphy@arm.com>
To: miles.chen@mediatek.com, Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
wsd_upstream@mediatek.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, iommu@lists.linux-foundation.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v3] dma-debug: fix incorrect pfn calculation
Date: Wed, 27 Sep 2017 11:23:52 +0100 [thread overview]
Message-ID: <273077fd-c5ad-82c8-60aa-cde89355e5e8@arm.com> (raw)
In-Reply-To: <1506484087-1177-1-git-send-email-miles.chen@mediatek.com>
[+DMA maintainers]
On 27/09/17 04:48, miles.chen@mediatek.com wrote:
> From: Miles Chen <miles.chen@mediatek.com>
>
> dma-debug reports the following warning:
>
> [name:panic&]WARNING: CPU: 3 PID: 298 at kernel-4.4/lib/dma-debug.c:604
> debug _dma_assert_idle+0x1a8/0x230()
> DMA-API: cpu touching an active dma mapped cacheline [cln=0x00000882300]
> CPU: 3 PID: 298 Comm: vold Tainted: G W O 4.4.22+ #1
> Hardware name: MT6739 (DT)
> Call trace:
> [<ffffff800808acd0>] dump_backtrace+0x0/0x1d4
> [<ffffff800808affc>] show_stack+0x14/0x1c
> [<ffffff800838019c>] dump_stack+0xa8/0xe0
> [<ffffff80080a0594>] warn_slowpath_common+0xf4/0x11c
> [<ffffff80080a061c>] warn_slowpath_fmt+0x60/0x80
> [<ffffff80083afe24>] debug_dma_assert_idle+0x1a8/0x230
> [<ffffff80081dca9c>] wp_page_copy.isra.96+0x118/0x520
> [<ffffff80081de114>] do_wp_page+0x4fc/0x534
> [<ffffff80081e0a14>] handle_mm_fault+0xd4c/0x1310
> [<ffffff8008098798>] do_page_fault+0x1c8/0x394
> [<ffffff800808231c>] do_mem_abort+0x50/0xec
>
> I found that debug_dma_alloc_coherent() and debug_dma_free_coherent()
> assume that dma_alloc_coherent() always returns a linear address.
> However it's possible that dma_alloc_coherent() returns a non-linear
> address. In this case, page_to_pfn(virt_to_page(virt)) will return an
> incorrect pfn. If the pfn is valid and mapped as a COW page,
> we will hit the warning when doing wp_page_copy().
Yeah, we definitely want that explanation recorded in the commit, since
the warning is pretty non-obvious otherwise.
Reviewed-by: Robin Murphy <robin.murphy@arm.com>
> Fix this by calculating pfn for linear and non-linear addresses.
>
> Signed-off-by: Miles Chen <miles.chen@mediatek.com>
> ---
> lib/dma-debug.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/lib/dma-debug.c b/lib/dma-debug.c
> index ea4cc3d..e5b4237 100644
> --- a/lib/dma-debug.c
> +++ b/lib/dma-debug.c
> @@ -1497,7 +1497,8 @@ void debug_dma_alloc_coherent(struct device *dev, size_t size,
>
> entry->type = dma_debug_coherent;
> entry->dev = dev;
> - entry->pfn = page_to_pfn(virt_to_page(virt));
> + entry->pfn = is_vmalloc_addr(virt) ? vmalloc_to_pfn(virt) :
> + page_to_pfn(virt_to_page(virt));
> entry->offset = offset_in_page(virt);
> entry->size = size;
> entry->dev_addr = dma_addr;
> @@ -1513,7 +1514,8 @@ void debug_dma_free_coherent(struct device *dev, size_t size,
> struct dma_debug_entry ref = {
> .type = dma_debug_coherent,
> .dev = dev,
> - .pfn = page_to_pfn(virt_to_page(virt)),
> + .pfn = is_vmalloc_addr(virt) ? vmalloc_to_pfn(virt) :
> + page_to_pfn(virt_to_page(virt)),
> .offset = offset_in_page(virt),
> .dev_addr = addr,
> .size = size,
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-09-27 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 3:48 miles.chen
2017-09-27 10:23 ` Robin Murphy [this message]
2017-10-01 8:04 ` Christoph Hellwig
2017-10-02 10:30 ` Miles Chen
2017-10-03 7:07 ` Christoph Hellwig
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=273077fd-c5ad-82c8-60aa-cde89355e5e8@arm.com \
--to=robin.murphy@arm.com \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=miles.chen@mediatek.com \
--cc=wsd_upstream@mediatek.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