mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: "zhaoyang.huang" <zhaoyang.huang@unisoc.com>,
	Sumit Semwal <sumit.semwal@linaro.org>,
	Benjamin Gaignard <benjamin.gaignard@collabora.com>,
	Brian Starkey <Brian.Starkey@arm.com>,
	John Stultz <jstultz@google.com>,
	"T . J . Mercier" <tjmercier@google.com>,
	"open list:DMA-BUF HEAPS FRAMEWORK" <linux-media@vger.kernel.org>,
	"open list:DMA-BUF HEAPS FRAMEWORK"
	<dri-devel@lists.freedesktop.org>,
	"moderated list:DMA-BUF HEAPS FRAMEWORK"
	<linaro-mm-sig@lists.linaro.org>,
	linux-kernel@vger.kernel.org,
	Zhaoyang Huang <huangzhaoyang@gmail.com>,
	steve.kang@unisoc.com
Subject: Re: [RFC PATCH] driver: dma-buf: use vmf_insert_page for cma_heap_vm_fault
Date: Wed, 15 Jan 2025 12:49:38 +0100	[thread overview]
Message-ID: <bfd19718-e7dc-45c4-8f86-34205e733916@amd.com> (raw)
In-Reply-To: <20250115061805.3495048-1-zhaoyang.huang@unisoc.com>

Am 15.01.25 um 07:18 schrieb zhaoyang.huang:
> From: Zhaoyang Huang <zhaoyang.huang@unisoc.com>
>
> When using dma-buf as memory pool for VMM. The vmf_insert_pfn will
> apply PTE_SPECIAL on pte which have vm_normal_page report bad_pte and
> return NULL. This commit would like to suggest to replace
> vmf_insert_pfn by vmf_insert_page.

Setting PTE_SPECIAL is completely intentional here to prevent 
get_user_pages() from working on DMA-buf mappings.

So absolutely clear NAK to this patch here.

What exactly are you trying to do?

Regards,
Christian.

>
> [  103.402787] kvm [5276]: gfn(ipa)=0x80000 hva=0x7d4a400000 write_fault=0
> [  103.403822] BUG: Bad page map in process crosvm_vcpu0  pte:168000140000f43 pmd:8000000c1ca0003
> [  103.405144] addr:0000007d4a400000 vm_flags:040400fb anon_vma:0000000000000000 mapping:ffffff8085163df0 index:0
> [  103.406536] file:dmabuf fault:cma_heap_vm_fault [cma_heap] mmap:dma_buf_mmap_internal read_folio:0x0
> [  103.407877] CPU: 3 PID: 5276 Comm: crosvm_vcpu0 Tainted: G        W  OE      6.6.46-android15-8-g8bab72b63c20-dirty-4k #1 1e474a12dac4553a3ebba3a911f3b744176a5d2d
> [  103.409818] Hardware name: Unisoc UMS9632-base Board (DT)
> [  103.410613] Call trace:
> [  103.411038] dump_backtrace+0xf4/0x140
> [  103.411641] show_stack+0x20/0x30
> [  103.412184] dump_stack_lvl+0x60/0x84
> [  103.412766] dump_stack+0x18/0x24
> [  103.413304] print_bad_pte+0x1b8/0x1cc
> [  103.413909] vm_normal_page+0xc8/0xd0
> [  103.414491] follow_page_pte+0xb0/0x304
> [  103.415096] follow_page_mask+0x108/0x240
> [  103.415721] __get_user_pages+0x168/0x4ac
> [  103.416342] __gup_longterm_locked+0x15c/0x864
> [  103.417023] pin_user_pages+0x70/0xcc
> [  103.417609] pkvm_mem_abort+0xf8/0x5c0
> [  103.418207] kvm_handle_guest_abort+0x3e0/0x3e4
> [  103.418906] handle_exit+0xac/0x33c
> [  103.419472] kvm_arch_vcpu_ioctl_run+0x48c/0x8d8
> [  103.420176] kvm_vcpu_ioctl+0x504/0x5bc
> [  103.420785] __arm64_sys_ioctl+0xb0/0xec
> [  103.421401] invoke_syscall+0x60/0x11c
> [  103.422000] el0_svc_common+0xb4/0xe8
> [  103.422590] do_el0_svc+0x24/0x30
> [  103.423131] el0_svc+0x3c/0x70
> [  103.423640] el0t_64_sync_handler+0x68/0xbc
> [  103.424288] el0t_64_sync+0x1a8/0x1ac
>
> Signed-off-by: Xiwei Wang <xiwei.wang1@unisoc.com>
> Signed-off-by: Aijun Sun <aijun.sun@unisoc.com>
> Signed-off-by: Zhaoyang Huang <zhaoyang.huang@unisoc.com>
> ---
>   drivers/dma-buf/heaps/cma_heap.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/dma-buf/heaps/cma_heap.c b/drivers/dma-buf/heaps/cma_heap.c
> index c384004b918e..b301fb63f16b 100644
> --- a/drivers/dma-buf/heaps/cma_heap.c
> +++ b/drivers/dma-buf/heaps/cma_heap.c
> @@ -168,7 +168,7 @@ static vm_fault_t cma_heap_vm_fault(struct vm_fault *vmf)
>   	if (vmf->pgoff > buffer->pagecount)
>   		return VM_FAULT_SIGBUS;
>   
> -	return vmf_insert_pfn(vma, vmf->address, page_to_pfn(buffer->pages[vmf->pgoff]));
> +	return vmf_insert_page(vma, vmf->address, buffer->pages[vmf->pgoff]);
>   }
>   
>   static const struct vm_operations_struct dma_heap_vm_ops = {


  reply	other threads:[~2025-01-15 11:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-15  6:18 zhaoyang.huang
2025-01-15 11:49 ` Christian König [this message]
2025-01-16  1:46   ` Zhaoyang Huang

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=bfd19718-e7dc-45c4-8f86-34205e733916@amd.com \
    --to=christian.koenig@amd.com \
    --cc=Brian.Starkey@arm.com \
    --cc=benjamin.gaignard@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=huangzhaoyang@gmail.com \
    --cc=jstultz@google.com \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=steve.kang@unisoc.com \
    --cc=sumit.semwal@linaro.org \
    --cc=tjmercier@google.com \
    --cc=zhaoyang.huang@unisoc.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®