From: Alex Deucher <alexander.deucher@amd.com> To: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org Cc: Alex Deucher <alexander.deucher@amd.com>, Felix Kuehling <Felix.Kuehling@amd.com> Subject: [PATCH 2/2] drm/ttm: Fix COW check Date: Thu, 8 Jul 2021 15:36:21 -0400 [thread overview] Message-ID: <20210708193621.2198733-2-alexander.deucher@amd.com> (raw) In-Reply-To: <20210708193621.2198733-1-alexander.deucher@amd.com> From: Felix Kuehling <Felix.Kuehling@amd.com> KFD Thunk maps invisible VRAM BOs with PROT_NONE, MAP_PRIVATE. is_cow_mapping returns true for these mappings. Add a check for vm_flags & VM_WRITE to avoid mmap failures on private read-only or PROT_NONE mappings. Fixes: f91142c62161 ("drm/ttm: nuke VM_MIXEDMAP on BO mappings v3") Signed-off-by: Felix Kuehling <Felix.Kuehling@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> --- drivers/gpu/drm/ttm/ttm_bo_vm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/ttm/ttm_bo_vm.c b/drivers/gpu/drm/ttm/ttm_bo_vm.c index f56be5bc0861..a75e90c7d4aa 100644 --- a/drivers/gpu/drm/ttm/ttm_bo_vm.c +++ b/drivers/gpu/drm/ttm/ttm_bo_vm.c @@ -552,7 +552,7 @@ static const struct vm_operations_struct ttm_bo_vm_ops = { int ttm_bo_mmap_obj(struct vm_area_struct *vma, struct ttm_buffer_object *bo) { /* Enforce no COW since would have really strange behavior with it. */ - if (is_cow_mapping(vma->vm_flags)) + if (is_cow_mapping(vma->vm_flags) && (vma->vm_flags & VM_WRITE)) return -EINVAL; ttm_bo_get(bo); -- 2.31.1
WARNING: multiple messages have this Message-ID (diff)
From: Alex Deucher <alexander.deucher@amd.com> To: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org Cc: Alex Deucher <alexander.deucher@amd.com>, Felix Kuehling <Felix.Kuehling@amd.com> Subject: [PATCH 2/2] drm/ttm: Fix COW check Date: Thu, 8 Jul 2021 15:36:21 -0400 [thread overview] Message-ID: <20210708193621.2198733-2-alexander.deucher@amd.com> (raw) In-Reply-To: <20210708193621.2198733-1-alexander.deucher@amd.com> From: Felix Kuehling <Felix.Kuehling@amd.com> KFD Thunk maps invisible VRAM BOs with PROT_NONE, MAP_PRIVATE. is_cow_mapping returns true for these mappings. Add a check for vm_flags & VM_WRITE to avoid mmap failures on private read-only or PROT_NONE mappings. Fixes: f91142c62161 ("drm/ttm: nuke VM_MIXEDMAP on BO mappings v3") Signed-off-by: Felix Kuehling <Felix.Kuehling@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> --- drivers/gpu/drm/ttm/ttm_bo_vm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/ttm/ttm_bo_vm.c b/drivers/gpu/drm/ttm/ttm_bo_vm.c index f56be5bc0861..a75e90c7d4aa 100644 --- a/drivers/gpu/drm/ttm/ttm_bo_vm.c +++ b/drivers/gpu/drm/ttm/ttm_bo_vm.c @@ -552,7 +552,7 @@ static const struct vm_operations_struct ttm_bo_vm_ops = { int ttm_bo_mmap_obj(struct vm_area_struct *vma, struct ttm_buffer_object *bo) { /* Enforce no COW since would have really strange behavior with it. */ - if (is_cow_mapping(vma->vm_flags)) + if (is_cow_mapping(vma->vm_flags) && (vma->vm_flags & VM_WRITE)) return -EINVAL; ttm_bo_get(bo); -- 2.31.1 _______________________________________________ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2021-07-08 19:36 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-08 19:36 [PATCH 1/2] drm/amdkfd: Allow CPU access for all VRAM BOs Alex Deucher 2021-07-08 19:36 ` Alex Deucher 2021-07-08 19:36 ` Alex Deucher [this message] 2021-07-08 19:36 ` [PATCH 2/2] drm/ttm: Fix COW check Alex Deucher 2021-07-09 6:38 ` Christian König 2021-07-09 6:38 ` Christian König 2021-07-09 7:52 ` Daniel Vetter 2021-07-09 7:52 ` Daniel Vetter 2021-07-09 19:31 ` Felix Kuehling 2021-07-09 19:31 ` Felix Kuehling 2021-07-09 19:37 ` Christian König 2021-07-09 19:37 ` Christian König 2021-07-10 0:29 ` Felix Kuehling 2021-07-10 0:29 ` Felix Kuehling 2021-07-12 9:27 ` Christian König 2021-07-12 9:27 ` Christian König
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=20210708193621.2198733-2-alexander.deucher@amd.com \ --to=alexander.deucher@amd.com \ --cc=Felix.Kuehling@amd.com \ --cc=amd-gfx@lists.freedesktop.org \ --cc=dri-devel@lists.freedesktop.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.