From 41c83aee073fdf45536fa27cafcda499ad64a478 Mon Sep 17 00:00:00 2001 From: Linus Torvalds Date: Mon, 19 Oct 2026 19:23:52 -1000 Subject: [PATCH] x86/xen: Fix a stale __get_user() reference in a comment The comment in set_aliased_prot() says the target address is faulted in with __get_user(), but the code has used copy_from_kernel_nofault() for a long time. Make the comment say so. Signed-off-by: Linus Torvalds --- arch/x86/xen/enlighten_pv.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/x86/xen/enlighten_pv.c b/arch/x86/xen/enlighten_pv.c index 2c64b388f616..c5117a7730d6 100644 --- a/arch/x86/xen/enlighten_pv.c +++ b/arch/x86/xen/enlighten_pv.c @@ -475,9 +475,9 @@ static void set_aliased_prot(void *v, pgprot_t prot) * have the same nominal mm, but if we're a kernel thread, lazy * mm dropping could change our pgd. * - * Out of an abundance of caution, this uses __get_user() to fault - * in the target address just in case there's some obscure case - * in which the target address isn't readable. + * Out of an abundance of caution, this uses copy_from_kernel_nofault() + * to fault in the target address just in case there's some obscure + * case in which the target address isn't readable. */ preempt_disable();