mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sohil Mehta <sohil.mehta@intel.com>
To: Dave Hansen <dave.hansen@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 13:16:08 -0700	[thread overview]
Message-ID: <f6f7a962-eae8-45e0-a8a5-ead0b9f37575@intel.com> (raw)
In-Reply-To: <6f8307dc-c3ab-4270-8215-c441f0e3f4c4@intel.com>

On 8/11/2025 12:22 PM, Dave Hansen wrote:
> 
> The changelog also isn't really converging, so I gave it a go to
> rewrite it. Is this missing anything?
> 

Thank you! Your changelog covers the essentials and makes it concise.
The dual nature of x86_task_fpu() was making it hard to write for me.

A couple of typos:

> This is because the AVX-512 timestamp code uses x86_task_fpu() doesn't
								^^^but> check it for NULL.

Missing "but"

> If anyone ever wants to track kernel thread AVX-512 use, the can come
> back later and do it properly, separate from this bug fix.

s/the/they

> https://git.kernel.org/pub/scm/linux/kernel/git/daveh/devel.git/commit/?h=testme&id=d61828dcbcff4ac80b91f5071ba6d21ef6c97347

It probably doesn't matter, but the documentation suggests ordering
Co-developed-by and Signed-off-by tags a bit differently.

"...every Co-developed-by: must be immediately followed by a
Signed-off-by: of the associated co-author."

https://www.kernel.org/doc/html/latest/process/submitting-patches.html#when-to-use-acked-by-cc-and-co-developed-by

Example of a patch submitted by a Co-developed-by: author:

From: From Author <from@author.example.org>

<changelog>

Co-developed-by: Random Co-Author <random@coauthor.example.org>
Signed-off-by: Random Co-Author <random@coauthor.example.org>
Signed-off-by: From Author <from@author.example.org>
Co-developed-by: Submitting Co-Author <sub@coauthor.example.org>
Signed-off-by: Submitting Co-Author <sub@coauthor.example.org>

  reply	other threads:[~2025-08-11 20:16 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
2025-08-11 20:16   ` Sohil Mehta [this message]
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=f6f7a962-eae8-45e0-a8a5-ead0b9f37575@intel.com \
    --to=sohil.mehta@intel.com \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=chang.seok.bae@intel.com \
    --cc=chao.gao@intel.com \
    --cc=dave.hansen@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=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®