arm: use mmap_write_(un)lock for copy_to_user
PATCH 1/1 arm: use mmap_write_(un)lock for copy_to_user
changes ARM's copy_to_user to use mmap_*write*_lock variants. This is because the data is written to user-space and not read.
--- arch/arm/lib/uaccess_with_memcpy.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
arch/arm/lib/uaccess_with_memcpy.c +4 -4
@@ -101,7 +101,7 @@ __copy_to_user_memcpy(void __user *to, const void *from, unsigned long n) atomic =faulthandler_disabled ();if (!atomic) -mmap_read_lock (current->mm); +mmap_write_lock (current->mm);while (n) {pte_t *pte;spinlock_t *ptl;
@@ -109,11 +109,11 @@ __copy_to_user_memcpy(void __user *to, const void *from, unsigned long n)while (!pin_page_for_write (to, &pte, &ptl)) {if (!atomic) -mmap_read_unlock (current->mm); +mmap_write_unlock (current->mm);if (__put_user (0 , (char __user *)to)) goto out;if (!atomic) -mmap_read_lock (current->mm); +mmap_write_lock (current->mm); } tocopy = (~(unsigned long )to & ~PAGE_MASK ) +1 ;
@@ -133,7 +133,7 @@ __copy_to_user_memcpy(void __user *to, const void *from, unsigned long n)spin_unlock (ptl); }if (!atomic) -mmap_read_unlock (current->mm); +mmap_write_unlock (current->mm); out:return n;
Signature · 7 lines
2.28.0 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Quoted 3 lines · Christian Lamparter
changes ARM's
copy_to_userto use mmap_*write*_lock variants. This is because the data is written to user-space and not read.
The mmap lock protects internals of 'struct mm_struct' and they do not change when the data is copied regardless of its direction.
Quoted 44 lines
Signed-off-by Christian Lamparter <[email protected]>--- arch/arm/lib/uaccess_with_memcpy.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)arch/arm/lib/uaccess_with_memcpy.c +4
-4@@ -101,7 +101,7 @@ __copy_to_user_memcpy(void __user *to, const void *from, unsigned long n) atomic =faulthandler_disabled ();if (!atomic) -mmap_read_lock (current->mm); +mmap_write_lock (current->mm);while (n) {pte_t *pte;spinlock_t *ptl;@@ -109,11 +109,11 @@ __copy_to_user_memcpy(void __user *to, const void *from, unsigned long n)while (!pin_page_for_write (to, &pte, &ptl)) {if (!atomic) -mmap_read_unlock (current->mm); +mmap_write_unlock (current->mm);if (__put_user (0 , (char __user *)to)) goto out;if (!atomic) -mmap_read_lock (current->mm); +mmap_write_lock (current->mm); } tocopy = (~(unsigned long )to & ~PAGE_MASK ) +1 ;@@ -133,7 +133,7 @@ __copy_to_user_memcpy(void __user *to, const void *from, unsigned long n)spin_unlock (ptl); }if (!atomic) -mmap_read_unlock (current->mm); +mmap_write_unlock (current->mm); out:return n;Signature · 1 line
2.28.0
Signature · 7 lines
Sincerely yours, Mike. _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Russell King - ARM Linux admin
maintainerQuoted 3 lines · Christian Lamparter
changes ARM's
copy_to_userto use mmap_*write*_lock variants. This is because the data is written to user-space and not read.
The "read" lock is there to ensure that the page tables are not changed (e.g. due to a page fault in another thread) while we are making changes to the page. It is a "read" lock because we can tolerate other threads reading the page tables and mm structures, but not making changes to those structures.
This has nothing to do with whether we are reading or writing userspace.
Therefore, your patch is incorrect.
What problem are you seeing?
Quoted 46 lines
Signed-off-by Christian Lamparter <[email protected]>--- arch/arm/lib/uaccess_with_memcpy.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)arch/arm/lib/uaccess_with_memcpy.c +4
-4@@ -101,7 +101,7 @@ __copy_to_user_memcpy(void __user *to, const void *from, unsigned long n) atomic =faulthandler_disabled ();if (!atomic) -mmap_read_lock (current->mm); +mmap_write_lock (current->mm);while (n) {pte_t *pte;spinlock_t *ptl;@@ -109,11 +109,11 @@ __copy_to_user_memcpy(void __user *to, const void *from, unsigned long n)while (!pin_page_for_write (to, &pte, &ptl)) {if (!atomic) -mmap_read_unlock (current->mm); +mmap_write_unlock (current->mm);if (__put_user (0 , (char __user *)to)) goto out;if (!atomic) -mmap_read_lock (current->mm); +mmap_write_lock (current->mm); } tocopy = (~(unsigned long )to & ~PAGE_MASK ) +1 ;@@ -133,7 +133,7 @@ __copy_to_user_memcpy(void __user *to, const void *from, unsigned long n)spin_unlock (ptl); }if (!atomic) -mmap_read_unlock (current->mm); +mmap_write_unlock (current->mm); out:return n;Signature · 1 line
2.28.0
Signature · 7 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last! _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Hello,
Quoted 12 lines · Russell King - ARM Linux admin
Quoted 3 lines · Christian Lamparter
changes ARM's
copy_to_userto use mmap_*write*_lock variants. This is because the data is written to user-space and not read.The "read" lock is there to ensure that the page tables are not changed (e.g. due to a page fault in another thread) while we are making changes to the page. It is a "read" lock because we can tolerate other threads reading the page tables and mm structures, but not making changes to those structures.
Quoted 3 lines
This has nothing to do with whether we are reading or writing userspace.
Therefore, your patch is incorrect.
I was looking at ARM's copy_to_user, because a faulty out-of-tree RPI patch that mixed read and write locks and this got me confused. Thanks to your excellent explanation, I now know as well that this patch is incorrect.
Cheers,
Christian
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel