archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <>
To: Jann Horn <>
Cc: stable <>,
	Security Officers <>,
	Peter Zijlstra <>,
	Will Deacon <>
Subject: Re: stable-backporting the VM_PFNMAP TLB flushing fix (b67fbebd4cf9)
Date: Mon, 29 Aug 2022 10:39:58 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Aug 29, 2022 at 10:38 AM Linus Torvalds
<> wrote:
> On Mon, Aug 29, 2022 at 10:36 AM Jann Horn <> wrote:
> >
> > A minimal but also completely different fix would be:
> Looks sane to me.

Just to clarify: we've fixed things in stable backports differently
from the development kernel before - just make sure that the commit
message mentions what the devel fix was and why the stable fix is
different, and it's all good.


      reply	other threads:[~2022-08-29 17:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 17:35 stable-backporting the VM_PFNMAP TLB flushing fix (b67fbebd4cf9) Jann Horn
2022-08-29 17:38 ` Linus Torvalds
2022-08-29 17:39   ` Linus Torvalds [this message]

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:

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

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).