apfs/linux-apfs
0
0
Fork 0
mirror of https://github.com/linux-apfs/linux-apfs.git synced 2026-05-01 15:00:59 -07:00
Code Issues Packages Projects Releases Wiki Activity

mm: replace access_remote_vm() write parameter with gup_flags

Browse Source 
This removes the 'write' argument from access_remote_vm() and replaces
it with 'gup_flags' as use of this function previously silently implied
FOLL_FORCE, whereas after this patch callers explicitly pass this flag.

We make this explicit as use of FOLL_FORCE can result in surprising
behaviour (and hence bugs) within the mm subsystem.

Signed-off-by: Lorenzo Stoakes <lstoakes@gmail.com>
Acked-by: Michal Hocko <mhocko@suse.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
Lorenzo Stoakes
2016-10-13 01:20:19 +01:00
committed by Linus Torvalds
parent 442486ec10
commit 6347e8d5bc
4 changed files with 20 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
mm/memory.c
+3 -8
View File
@@ -3935,19 +3935,14 @@ static int __access_remote_vm(struct task_struct *tsk, struct mm_struct *mm,
* @addr: start address to access
* @buf: source or destination buffer
* @len: number of bytes to transfer
* @write: whether the access is a write
* @gup_flags: flags modifying lookup behaviour
*
* The caller must hold a reference on @mm.
*/
int access_remote_vm(struct mm_struct *mm, unsigned long addr,
void *buf, int len, int write)
void *buf, int len, unsigned int gup_flags)
{
unsigned int flags = FOLL_FORCE;
if (write)
flags |= FOLL_WRITE;
return __access_remote_vm(NULL, mm, addr, buf, len, flags);
return __access_remote_vm(NULL, mm, addr, buf, len, gup_flags);
}
/*