From: Dave Hansen <dave.hansen@intel.com>
To: Sohil Mehta <sohil.mehta@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org
Cc: Borislav Petkov <bp@alien8.de>, "H . Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Vignesh Balasubramanian <vigbalas@amd.com>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Oleg Nesterov <oleg@redhat.com>,
"Chang S . Bae" <chang.seok.bae@intel.com>,
Brian Gerst <brgerst@gmail.com>,
Eric Biggers <ebiggers@google.com>, Kees Cook <kees@kernel.org>,
Chao Gao <chao.gao@intel.com>,
Christoph Hellwig <hch@infradead.org>,
Fushuai Wang <wangfushuai@baidu.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] x86/fpu: Fix NULL dereference in avx512_status()
Date: Mon, 11 Aug 2025 12:22:16 -0700 [thread overview]
Message-ID: <6f8307dc-c3ab-4270-8215-c441f0e3f4c4@intel.com> (raw)
In-Reply-To: <20250811185044.2227268-1-sohil.mehta@intel.com>
On 8/11/25 11:50, Sohil Mehta wrote:
> From: Fushuai Wang <wangfushuai@baidu.com>
>
> Problem
> -------
> With CONFIG_X86_DEBUG_FPU enabled, reading /proc/[kthread]/arch_status
> causes a kernel NULL pointer dereference.
<snip>
That changelog is getting a bit long-winded and has a lot of extra
information.
The changelog also isn't really converging, so I gave it a go to
rewrite it. Is this missing anything?
https://git.kernel.org/pub/scm/linux/kernel/git/daveh/devel.git/commit/?h=testme&id=d61828dcbcff4ac80b91f5071ba6d21ef6c97347
next prev parent reply other threads:[~2025-08-11 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 18:50 Sohil Mehta
2025-08-11 19:22 ` Dave Hansen [this message]
2025-08-11 20:16 ` Sohil Mehta
2025-08-11 20:29 ` Dave Hansen
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=6f8307dc-c3ab-4270-8215-c441f0e3f4c4@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=chang.seok.bae@intel.com \
--cc=chao.gao@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=ebiggers@google.com \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=kees@kernel.org \
--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=sohil.mehta@intel.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®