From: sashiko-bot@kernel.org
To: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Cc: linux-s390@vger.kernel.org, "Heiko Carstens" <hca@linux.ibm.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>
Subject: Re: [PATCH v2] arch, mm: promote DEBUG_WX to CHECK_WX
Date: Sat, 26 Sep 2026 09:38:04 +0000 [thread overview]
Message-ID: <20260926093805.0299A1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260926-direct-map-verify-wx-v2-1-efcd64a6b74a@kernel.org>
> Verification that the kernel does not have writable + executable
> mappings is about detecting security risks rather than a pure debug
> feature.
>
> Major distribution configurations enable it in their kernels as well as
> defconfigs of most architectures that have ARCH_HAS_DEBUG_WX.
>
> Rename relevant generic configuration options to use CHECK_WX and move
> their definitions from mm/Kconfig.debug to mm/Kconfig.
>
> Rename *debug_checkwx() funcitons and macros to *pgtable_checkwx().
>
> For arm that does not widely enable it, only rename its variants of the
> config options.
>
> Enabling CHECK_WX adds a few kilobytes to the kernel binary and while
> the added size can be slightly reduced with churny updates of
> architecture implementations of ptdump, the core functionality takes
> most of the added size. It cannot be moved to .init.text because the
> verification has to happen after init sections are freed.
>
> With this, make generic CHECK_WX default to STRICT_KERNEL_RWX while
> still leaving users targeting small kernels the possibility to opt-out.
>
> Suggested-by: Dave Hansen <dave.hansen@linux.intel.com>
> Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260926-direct-map-verify-wx-v2-1-efcd64a6b74a@kernel.org?part=1
next prev parent reply other threads:[~2026-09-26 9:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 9:29 [PATCH v2] arch, mm: promote DEBUG_WX to CHECK_WX Mike Rapoport (Microsoft)
2026-09-26 9:29 ` Mike Rapoport (Microsoft)
2026-09-26 9:33 ` Lorenzo Stoakes (ARM)
2026-09-26 9:33 ` Lorenzo Stoakes (ARM)
2026-09-26 9:38 ` sashiko-bot [this message]
2026-09-28 5:54 ` Anshuman Khandual
2026-09-28 5:54 ` Anshuman Khandual
2026-09-30 9:51 ` Mike Rapoport
2026-09-30 9:51 ` Mike Rapoport
2026-10-01 3:17 ` Anshuman Khandual
2026-10-01 3:17 ` Anshuman Khandual
2026-09-28 14:03 ` Dave Hansen
2026-09-28 14:03 ` Dave Hansen
2026-09-30 9:54 ` David Hildenbrand (Arm)
2026-09-30 9:54 ` David Hildenbrand (Arm)
2026-10-01 3:43 ` Anshuman Khandual
2026-10-01 3:43 ` Anshuman Khandual
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=20260926093805.0299A1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.