From: Sohil Mehta <sohil.mehta@intel.com>
To: Fushuai Wang <wangfushuai@baidu.com>
Cc: <aruna.ramakrishna@oracle.com>, <aubrey.li@intel.com>,
<bp@alien8.de>, <brgerst@gmail.com>, <chang.seok.bae@intel.com>,
<dave.hansen@linux.intel.com>, <hpa@zytor.com>,
<linux-kernel@vger.kernel.org>, <mingo@redhat.com>,
<oleg@redhat.com>, <peterz@infradead.org>,
<rick.p.edgecombe@intel.com>, <seanjc@google.com>,
<tglx@linutronix.de>, <vigbalas@amd.com>, <x86@kernel.org>
Subject: Re: [PATCH] x86/fpu: Fix potential NULL dereference in avx512_status()
Date: Fri, 18 Jul 2025 16:48:06 -0700 [thread overview]
Message-ID: <99baa18c-ae1c-47e1-8bbe-e411570df8f1@intel.com> (raw)
In-Reply-To: <20250718071250.36019-1-wangfushuai@baidu.com>
>> I am wondering if we ever need to expose the AVX512 usage for kernel
>> threads? If not, then we can do what you currently have but without the
>> CONFIG_X86_DEBUG_FPU restriction. All kernel threads would always print
>> the AVX512_elapsed_ms as -1.
>>
Let's go with this approach. See below.
>> However, this would be a user visible change so we should probably get
>> more inputs. I tried this experiment on an older kernel without the
>> above issue. Among all the active kthreads on my system a handful of
>> them show a valid value for AVX512 usage. The rest of them all show -1.
>>
>> PID: 2594
>> CMD: avahi-daemon: running [SAP.local]
>> /proc/2594/arch_status content:
>> AVX512_elapsed_ms: 46032
>>
>> PID: 2729
>> CMD: sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups
>> /proc/2729/arch_status content:
>> AVX512_elapsed_ms: 396656
>>
Correction: These aren't really Kthreads. There was a slight error in
the script that I used.
Reporting AVX512 usage doesn't seem very useful for Kthreads. The usage
is mainly for userspace schedulers. Let's just report -1 for all Kthreads.
How about something like below. This should work with and without
CONFIG_X86_DEBUG_FPU.
diff --git a/arch/x86/kernel/fpu/xstate.c b/arch/x86/kernel/fpu/xstate.c
index 9aa9ac8399ae..10c3994295f2 100644
--- a/arch/x86/kernel/fpu/xstate.c
+++ b/arch/x86/kernel/fpu/xstate.c
@@ -1855,19 +1855,18 @@ long fpu_xstate_prctl(int option, unsigned long
arg2)
#ifdef CONFIG_PROC_PID_ARCH_STATUS
/*
* Report the amount of time elapsed in millisecond since last AVX512
- * use in the task.
+ * use in the task. Report -1 if no AVX512 usage.
*/
static void avx512_status(struct seq_file *m, struct task_struct *task)
{
- unsigned long timestamp =
READ_ONCE(x86_task_fpu(task)->avx512_timestamp);
- long delta;
+ unsigned long timestamp = 0;
+ long delta = -1;
- if (!timestamp) {
- /*
- * Report -1 if no AVX512 usage
- */
- delta = -1;
- } else {
+ /* Do not report AVX512 usage for kernel threads */
+ if (!(task->flags & (PF_KTHREAD | PF_USER_WORKER)))
+ timestamp = READ_ONCE(x86_task_fpu(task)->avx512_timestamp);
+
+ if (timestamp) {
delta = (long)(jiffies - timestamp);
/*
* Cap to LONG_MAX if time difference > LONG_MAX
next prev parent reply other threads:[~2025-07-18 23:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 9:43 Fushuai Wang
2025-07-17 19:21 ` Sohil Mehta
2025-07-18 6:21 ` Sohil Mehta
2025-07-18 7:12 ` Fushuai Wang
2025-07-18 23:48 ` Sohil Mehta [this message]
2025-07-21 14:09 ` Dave Hansen
2025-07-22 5:35 ` Christoph Hellwig
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=99baa18c-ae1c-47e1-8bbe-e411570df8f1@intel.com \
--to=sohil.mehta@intel.com \
--cc=aruna.ramakrishna@oracle.com \
--cc=aubrey.li@intel.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vigbalas@amd.com \
--cc=wangfushuai@baidu.com \
--cc=x86@kernel.org \
/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®