rust-uaccess-use-inline_copy_to_user-to-guard-copy_to_user.patch removed from -mm tree
The quilt patch titled
Subject: rust: uaccess: use INLINE_COPY_TO_USER to guard copy_to_user()
has been removed from the -mm tree. Its filename was
rust-uaccess-use-inline_copy_to_user-to-guard-copy_to_user.patch
This patch was dropped because it was merged into the mm-nonmm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Yury Norov <[email protected]>
Subject: rust: uaccess: use INLINE_COPY_TO_USER to guard copy_to_user()
Date: Fri, 24 Apr 2026 22:08:55 -0400
Patch series "uaccess: unify inline vs outline copy_{from,to}_user() selection", v2.
The kernel allows arches to select between inline and outline implementations of the copy_{from,to}_user() by defining individual INLINE_COPY_FROM_USER and INLINE_COPY_TO_USER, correspondingly. However, all arches enable or disable them always together.
Without the real use-case for one helper being inlined while the other outlined, having independent controls is excessive and error prone.
The first patch of the series fixes rust/uaccess coppy_to_user() wrapper guarded with INLINE_COPY_FROM_USER. The 2nd patch switches codebase to the unified INLINE_COPY_USER. And the last patch cleans up ifdefery in the include/linux/uaccess.h
This patch (of 3):
The copy_to_user() rust helper is only needed when the main kernel inlines the function. It is controlled by INLINE_COPY_TO_USER, but the rust helper is protected with INLINE_COPY_FROM_USER.
Fix that.
---
rust/helpers/uaccess.c | 2 ++ 1 file changed, 2 insertions(+)
rust/helpers/uaccess.c renamed from rust/helpers/uaccess.c~rust-uaccess-use-inline_copy_to_user-to-guard-copy_to_user +2 -0
@@ -20,7 +20,9 @@ unsigned long rust_helper__copy_from_use {return _inline_copy_from_user (to, from, n); } +#endif +#ifdef INLINE_COPY_TO_USER __rust_helper unsigned long rust_helper__copy_to_user (void __user *to,const void *from,unsigned long n) {
_
Patches currently in -mm which might be from [email protected] are