mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	"Aurelien Jarno" <aurel32@debian.org>
Subject: Re: [PATCH] MIPS: kernel: Clear FPU states when setting up kernel threads
Date: Fri, 01 Dec 2023 11:12:21 +0000	[thread overview]
Message-ID: <6f290f4b-5dc2-44f3-9f2d-01496f78d629@app.fastmail.com> (raw)
In-Reply-To: <20231130163601.185270-1-tsbogend@alpha.franken.de>



在2023年11月30日十一月 下午4:36,Thomas Bogendoerfer写道:
> io_uring sets up the io worker kernel thread via a syscall out of an
> user space prrocess. This process might have used FPU and since
> copy_thread() didn't clear FPU states for kernel threads a BUG()
> is triggered for using FPU inside kernel. Move code around
> to always clear FPU state for user and kernel threads.
>
> Cc: stable@vger.kernel.org
> Reported-by: Aurelien Jarno <aurel32@debian.org>
> Closes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055021
> Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

Reviewed-by: Jiaxun Yang <jiaxun.yang@flygoat.com>

Perhaps
Suggested-by: Jiaxun Yang <jiaxun.yang@flygoat.com>

As well :-)

Thanks
- Jiaxun
> ---
>  arch/mips/kernel/process.c | 25 +++++++++++++------------
>  1 file changed, 13 insertions(+), 12 deletions(-)
>
> diff --git a/arch/mips/kernel/process.c b/arch/mips/kernel/process.c
> index 5387ed0a5186..b630604c577f 100644
> --- a/arch/mips/kernel/process.c
> +++ b/arch/mips/kernel/process.c
> @@ -121,6 +121,19 @@ int copy_thread(struct task_struct *p, const 
> struct kernel_clone_args *args)
>  	/*  Put the stack after the struct pt_regs.  */
>  	childksp = (unsigned long) childregs;
>  	p->thread.cp0_status = (read_c0_status() & ~(ST0_CU2|ST0_CU1)) | 
> ST0_KERNEL_CUMASK;
> +
> +	/*
> +	 * New tasks lose permission to use the fpu. This accelerates context
> +	 * switching for most programs since they don't use the fpu.
> +	 */
> +	clear_tsk_thread_flag(p, TIF_USEDFPU);
> +	clear_tsk_thread_flag(p, TIF_USEDMSA);
> +	clear_tsk_thread_flag(p, TIF_MSA_CTX_LIVE);
> +
> +#ifdef CONFIG_MIPS_MT_FPAFF
> +	clear_tsk_thread_flag(p, TIF_FPUBOUND);
> +#endif /* CONFIG_MIPS_MT_FPAFF */
> +
>  	if (unlikely(args->fn)) {
>  		/* kernel thread */
>  		unsigned long status = p->thread.cp0_status;
> @@ -149,20 +162,8 @@ int copy_thread(struct task_struct *p, const 
> struct kernel_clone_args *args)
>  	p->thread.reg29 = (unsigned long) childregs;
>  	p->thread.reg31 = (unsigned long) ret_from_fork;
> 
> -	/*
> -	 * New tasks lose permission to use the fpu. This accelerates context
> -	 * switching for most programs since they don't use the fpu.
> -	 */
>  	childregs->cp0_status &= ~(ST0_CU2|ST0_CU1);
> 
> -	clear_tsk_thread_flag(p, TIF_USEDFPU);
> -	clear_tsk_thread_flag(p, TIF_USEDMSA);
> -	clear_tsk_thread_flag(p, TIF_MSA_CTX_LIVE);
> -
> -#ifdef CONFIG_MIPS_MT_FPAFF
> -	clear_tsk_thread_flag(p, TIF_FPUBOUND);
> -#endif /* CONFIG_MIPS_MT_FPAFF */
> -
>  #ifdef CONFIG_MIPS_FP_SUPPORT
>  	atomic_set(&p->thread.bd_emu_frame, BD_EMUFRAME_NONE);
>  #endif
> -- 
> 2.35.3

-- 
- Jiaxun

  reply	other threads:[~2023-12-01 11:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30 16:36 Thomas Bogendoerfer
2023-12-01 11:12 ` Jiaxun Yang [this message]
2023-12-05 17:52   ` Thomas Bogendoerfer
2023-12-05 17:51 ` Thomas Bogendoerfer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6f290f4b-5dc2-44f3-9f2d-01496f78d629@app.fastmail.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=aurel32@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®