[PATCH] i386: Update __copy_to_user_inatomic linuxdoc description
Explicity specify that the caller should pin the user memory otherwise the function will sleep Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@gmail.com> Signed-off-by: Andi Kleen <ak@suse.de>
This commit is contained in:
parent
c8fdd24725
commit
6d1c426158
1 changed files with 13 additions and 1 deletions
|
@ -397,7 +397,19 @@ unsigned long __must_check __copy_from_user_ll_nocache(void *to,
|
|||
unsigned long __must_check __copy_from_user_ll_nocache_nozero(void *to,
|
||||
const void __user *from, unsigned long n);
|
||||
|
||||
/*
|
||||
/**
|
||||
* __copy_to_user_inatomic: - Copy a block of data into user space, with less checking.
|
||||
* @to: Destination address, in user space.
|
||||
* @from: Source address, in kernel space.
|
||||
* @n: Number of bytes to copy.
|
||||
*
|
||||
* Context: User context only.
|
||||
*
|
||||
* Copy data from kernel space to user space. Caller must check
|
||||
* the specified block with access_ok() before calling this function.
|
||||
* The caller should also make sure he pins the user space address
|
||||
* so that the we don't result in page fault and sleep.
|
||||
*
|
||||
* Here we special-case 1, 2 and 4-byte copy_*_user invocations. On a fault
|
||||
* we return the initial request size (1, 2 or 4), as copy_*_user should do.
|
||||
* If a store crosses a page boundary and gets a fault, the x86 will not write
|
||||
|
|
Loading…
Reference in a new issue