From: Ingo Molnar <mingo@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"Borislav Petkov (AMD)" <bp@alien8.de>,
Kees Cook <keescook@chromium.org>,
"Mike Rapoport (IBM)" <rppt@kernel.org>,
David Hildenbrand <david@redhat.com>,
Pengfei Xu <pengfei.xu@intel.com>,
John Allen <john.allen@amd.com>,
x86@kernel.org
Subject: Re: [tip: x86/shstk] mm: Don't allow write GUPs to shadow stack memory
Date: Fri, 21 Jul 2023 10:34:04 +0200 [thread overview]
Message-ID: <ZLpC/IbswCA0yUHD@gmail.com> (raw)
In-Reply-To: <168980685456.28540.8149705038742119504.tip-bot2@tip-bot2>
* tip-bot2 for Rick Edgecombe <tip-bot2@linutronix.de> wrote:
> The following commit has been merged into the x86/shstk branch of tip:
>
> Commit-ID: 7c8f82db8acb9f0935703c0d96cda552bbf91ff2
> Gitweb: https://git.kernel.org/tip/7c8f82db8acb9f0935703c0d96cda552bbf91ff2
> Author: Rick Edgecombe <rick.p.edgecombe@intel.com>
> AuthorDate: Mon, 12 Jun 2023 17:10:48 -07:00
> Committer: Rick Edgecombe <rick.p.edgecombe@intel.com>
> CommitterDate: Tue, 11 Jul 2023 14:12:47 -07:00
>
> mm: Don't allow write GUPs to shadow stack memory
JFYI, this commit was the last user of writable_file_mapping_allowed(),
which breaks the x86-defconfig build:
mm/gup.c:1015:13: error: ‘writable_file_mapping_allowed’ defined but not used [-Werror=unused-function]
There's also a now orphan reference to writable_file_mapping_allowed() in
the comment of folio_fast_pin_allowed().
Thanks,
Ingo
next prev parent reply other threads:[~2023-07-21 8:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 22:47 [tip: x86/shstk] mm: Don't allow write GUPs to shadow stack memory tip-bot2 for Rick Edgecombe
2023-07-21 8:34 ` Ingo Molnar [this message]
2023-07-21 16:24 ` Edgecombe, Rick P
2023-07-26 18:11 ` Edgecombe, Rick P
-- strict thread matches above, loose matches on Subject: below --
2023-08-02 22:19 tip-bot2 for Rick Edgecombe
2023-06-16 19:16 tip-bot2 for Rick Edgecombe
2023-03-20 16:39 tip-bot2 for Rick Edgecombe
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=ZLpC/IbswCA0yUHD@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=john.allen@amd.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=pengfei.xu@intel.com \
--cc=rick.p.edgecombe@intel.com \
--cc=rppt@kernel.org \
--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 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.