All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Aaron Lu <aaron.lu@intel.com>
Cc: security@kernel.org, lkml <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Andy Lutomirski <luto@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@suse.com>,
	Logan Gunthorpe <logang@deltatee.com>
Subject: Re: [PATCH 1/1] x86/mm: Use proper mask when setting PUD mapping
Date: Fri, 19 Aug 2022 09:02:14 +0200	[thread overview]
Message-ID: <Yv81dihastDVE3Po@kroah.com> (raw)
In-Reply-To: <Yv71qbuHkSsLGhvJ@ziqianlu-desk1>

On Fri, Aug 19, 2022 at 10:30:01AM +0800, Aaron Lu wrote:
> commit c164fbb40c43f("x86/mm: thread pgprot_t through
> init_memory_mapping()") mistakenly used __pgprot() which doesn't
> respect __default_kernel_pte_mask when setting PUD mapping, fix it
> by using __pgprot_mask().
> 
> Fixes: c164fbb40c43f("x86/mm: thread pgprot_t through init_memory_mapping()")

Nit, you need a space before the '(' character or the linux-next scripts
will complain :(

Also, you cc:ed security@k.o and lkml.  As this is public, no need to
copy security@k.o at all.

thanks,

greg k-h

      parent reply	other threads:[~2022-08-19  7:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19  2:28 [PATCH 0/1] Use proper mask when setting PUD mapping Aaron Lu
2022-08-19  2:30 ` [PATCH 1/1] x86/mm: " Aaron Lu
2022-08-19  3:08   ` Linus Torvalds
2022-08-19  7:02   ` Greg KH [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:
  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=Yv81dihastDVE3Po@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=aaron.lu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=luto@kernel.org \
    --cc=mhocko@suse.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=security@kernel.org \
    --cc=tglx@linutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.