LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: <miles.chen@mediatek.com> To: Christoph Hellwig <hch@lst.de>, Marek Szyprowski <m.szyprowski@samsung.com>, Robin Murphy <robin.murphy@arm.com> Cc: <linux-kernel@vger.kernel.org>, <iommu@lists.linux-foundation.org>, <linux-mediatek@lists.infradead.org>, <wsd_upstream@mediatek.com>, Miles Chen <miles.chen@mediatek.com> Subject: [PATCH v5] dma-debug: fix incorrect pfn calculation Date: Thu, 23 Nov 2017 17:42:09 +0800 [thread overview] Message-ID: <1511430129-4210-1-git-send-email-miles.chen@mediatek.com> (raw) 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(). Fix this by calculating pfn for linear and non-linear addresses. Some changes are added to this patch according to Christoph's comment in patch v3 and a bugfix in patch v4: a. use normal if/else statement for better readability b. exclude non-linear and non-vmalloc addresses c. use virt_addr_valid() to check linear addresses Signed-off-by: Miles Chen <miles.chen@mediatek.com> --- lib/dma-debug.c | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-) diff --git a/lib/dma-debug.c b/lib/dma-debug.c index ea4cc3d..4c08eb6 100644 --- a/lib/dma-debug.c +++ b/lib/dma-debug.c @@ -1495,14 +1495,22 @@ void debug_dma_alloc_coherent(struct device *dev, size_t size, if (!entry) return; + /* handle vmalloc and linear addresses */ + if (!is_vmalloc_addr(virt) && !virt_addr_valid(virt)) + return; + entry->type = dma_debug_coherent; entry->dev = dev; - entry->pfn = page_to_pfn(virt_to_page(virt)); entry->offset = offset_in_page(virt); entry->size = size; entry->dev_addr = dma_addr; entry->direction = DMA_BIDIRECTIONAL; + if (is_vmalloc_addr(virt)) + entry->pfn = vmalloc_to_pfn(virt); + else + entry->pfn = page_to_pfn(virt_to_page(virt)); + add_dma_entry(entry); } EXPORT_SYMBOL(debug_dma_alloc_coherent); @@ -1513,13 +1521,21 @@ 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)), .offset = offset_in_page(virt), .dev_addr = addr, .size = size, .direction = DMA_BIDIRECTIONAL, }; + /* handle vmalloc and linear addresses */ + if (!is_vmalloc_addr(virt) && !virt_addr_valid(virt)) + return; + + if (is_vmalloc_addr(virt)) + ref.pfn = vmalloc_to_pfn(virt); + else + ref.pfn = page_to_pfn(virt_to_page(virt)); + if (unlikely(dma_debug_disabled())) return; -- 1.9.1
reply other threads:[~2017-11-23 9:42 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1511430129-4210-1-git-send-email-miles.chen@mediatek.com \ --to=miles.chen@mediatek.com \ --cc=hch@lst.de \ --cc=iommu@lists.linux-foundation.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mediatek@lists.infradead.org \ --cc=m.szyprowski@samsung.com \ --cc=robin.murphy@arm.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: linkBe 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; as well as URLs for NNTP newsgroup(s).