From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Andrey Kalachev <kalachev@swemel.ru>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH v5.4-v6.1] udmabuf: use vmf_insert_pfn and VM_PFNMAP for handling mmap
Date: Wed, 4 Dec 2024 10:41:51 -0500 [thread overview]
Message-ID: <20241204102728-fdfe0de6777432df@stable.kernel.org> (raw)
In-Reply-To: <20241204151735.141277-3-kalachev@swemel.ru>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 7d79cd784470395539bda91bf0b3505ff5b2ab6d
WARNING: Author mismatch between patch and upstream commit:
Backport author: Andrey Kalachev <kalachev@swemel.ru>
Commit author: Vivek Kasireddy <vivek.kasireddy@intel.com>
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.11.y | Present (exact SHA1)
6.6.y | Not found
6.1.y | Not found
Note: The patch differs from the upstream commit:
---
1: 7d79cd7844703 ! 1: 14a0c0b74cf0d udmabuf: use vmf_insert_pfn and VM_PFNMAP for handling mmap
@@ Metadata
## Commit message ##
udmabuf: use vmf_insert_pfn and VM_PFNMAP for handling mmap
+ [ Upstream commit 7d79cd784470395539bda91bf0b3505ff5b2ab6d ]
+
Add VM_PFNMAP to vm_flags in the mmap handler to ensure that the mappings
would be managed without using struct page.
@@ Commit message
Cc: Oscar Salvador <osalvador@suse.de>
Cc: Shuah Khan <shuah@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
+ Reported-by: syzbot+3d218f7b6c5511a83a79@syzkaller.appspotmail.com
+ [ Andrey: Backport required minor change: replace call
+ to vm_flags_set() in mmap_udmabuf() by direct
+ modification of the vma->vm_flags, because the set
+ of vm_flags_*() functions is not in this versions. ]
+ Signed-off-by: Andrey Kalachev <kalachev@swemel.ru>
## drivers/dma-buf/udmabuf.c ##
@@ drivers/dma-buf/udmabuf.c: static vm_fault_t udmabuf_vm_fault(struct vm_fault *vmf)
@@ drivers/dma-buf/udmabuf.c: static int mmap_udmabuf(struct dma_buf *buf, struct v
vma->vm_ops = &udmabuf_vm_ops;
vma->vm_private_data = ubuf;
-+ vm_flags_set(vma, VM_PFNMAP | VM_DONTEXPAND | VM_DONTDUMP);
++ vma->vm_flags |= VM_PFNMAP | VM_DONTEXPAND | VM_DONTDUMP;
return 0;
}
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
| stable/linux-5.4.y | Success | Success |
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Andrey Kalachev <kalachev@swemel.ru>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH v5.4-v6.1] udmabuf: use vmf_insert_pfn and VM_PFNMAP for handling mmap
Date: Wed, 4 Dec 2024 17:11:32 -0500 [thread overview]
Message-ID: <20241204102728-fdfe0de6777432df@stable.kernel.org> (raw)
Message-ID: <20241204221132.S3MDwZ543W4SBazszrn-HzL-eh0El3BkItJyU8CmIig@z> (raw)
In-Reply-To: <20241204151735.141277-3-kalachev@swemel.ru>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 7d79cd784470395539bda91bf0b3505ff5b2ab6d
WARNING: Author mismatch between patch and upstream commit:
Backport author: Andrey Kalachev <kalachev@swemel.ru>
Commit author: Vivek Kasireddy <vivek.kasireddy@intel.com>
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.11.y | Present (exact SHA1)
6.6.y | Not found
6.1.y | Not found
Note: The patch differs from the upstream commit:
---
1: 7d79cd7844703 ! 1: 14a0c0b74cf0d udmabuf: use vmf_insert_pfn and VM_PFNMAP for handling mmap
@@ Metadata
## Commit message ##
udmabuf: use vmf_insert_pfn and VM_PFNMAP for handling mmap
+ [ Upstream commit 7d79cd784470395539bda91bf0b3505ff5b2ab6d ]
+
Add VM_PFNMAP to vm_flags in the mmap handler to ensure that the mappings
would be managed without using struct page.
@@ Commit message
Cc: Oscar Salvador <osalvador@suse.de>
Cc: Shuah Khan <shuah@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
+ Reported-by: syzbot+3d218f7b6c5511a83a79@syzkaller.appspotmail.com
+ [ Andrey: Backport required minor change: replace call
+ to vm_flags_set() in mmap_udmabuf() by direct
+ modification of the vma->vm_flags, because the set
+ of vm_flags_*() functions is not in this versions. ]
+ Signed-off-by: Andrey Kalachev <kalachev@swemel.ru>
## drivers/dma-buf/udmabuf.c ##
@@ drivers/dma-buf/udmabuf.c: static vm_fault_t udmabuf_vm_fault(struct vm_fault *vmf)
@@ drivers/dma-buf/udmabuf.c: static int mmap_udmabuf(struct dma_buf *buf, struct v
vma->vm_ops = &udmabuf_vm_ops;
vma->vm_private_data = ubuf;
-+ vm_flags_set(vma, VM_PFNMAP | VM_DONTEXPAND | VM_DONTDUMP);
++ vma->vm_flags |= VM_PFNMAP | VM_DONTEXPAND | VM_DONTDUMP;
return 0;
}
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
| stable/linux-5.4.y | Success | Success |
next prev parent reply other threads:[~2024-12-04 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 15:17 Please, fix syzbot crash: kernel BUG in filemap_unaccount_folio Andrey Kalachev
2024-12-04 15:17 ` [PATCH v6.6] udmabuf: use vmf_insert_pfn and VM_PFNMAP for handling mmap Andrey Kalachev
2024-12-04 15:41 ` Sasha Levin
2024-12-04 22:12 ` Sasha Levin
2024-12-04 15:17 ` [PATCH v5.4-v6.1] " Andrey Kalachev
2024-12-04 15:41 ` Sasha Levin [this message]
2024-12-04 22:11 ` Sasha Levin
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=20241204102728-fdfe0de6777432df@stable.kernel.org \
--to=sashal@kernel.org \
--cc=kalachev@swemel.ru \
--cc=stable@vger.kernel.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: link
Be 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.