From: patchwork-bot+linux-riscv@kernel.org
To: Mike Rapoport <rppt@kernel.org>
Cc: linux-riscv@lists.infradead.org, akpm@linux-foundation.org,
aou@eecs.berkeley.edu, agordeev@linux.ibm.com, alex@ghiti.fr,
bp@alien8.de, catalin.marinas@arm.com, chleroy@kernel.org,
borntraeger@linux.ibm.com, dave.hansen@linux.intel.com,
david@kernel.org, gerald.schaefer@linux.ibm.com,
hca@linux.ibm.com, mingo@redhat.com, liam@infradead.org,
ljs@kernel.org, maddy@linux.ibm.com, mark.rutland@arm.com,
mpe@ellerman.id.au, mhocko@suse.com, npiggin@gmail.com,
palmer@dabbelt.com, pjw@kernel.org, hpa@zytor.com,
ritesh.list@gmail.com, linux@armlinux.org.uk,
sshegde@linux.ibm.com, surenb@google.com, svens@linux.ibm.com,
tglx@kernel.org, gor@linux.ibm.com, vbabka@kernel.org,
will@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH v2] arch, mm: promote DEBUG_WX to CHECK_WX
Date: Sun, 01 Nov 2026 22:16:45 +0000 [thread overview]
Message-ID: <179357140534.2624073.9989407542230376185.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260926-direct-map-verify-wx-v2-1-efcd64a6b74a@kernel.org>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Andrew Morton <akpm@linux-foundation.org>:
On Sat, 26 Sep 2026 12:29:29 +0300 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [v2] arch, mm: promote DEBUG_WX to CHECK_WX
https://git.kernel.org/riscv/c/2e83e2ce34ff
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-01 22:16 UTC|newest]
Thread overview: 9+ 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:33 ` Lorenzo Stoakes (ARM)
2026-09-28 5:54 ` Anshuman Khandual
2026-09-30 9:51 ` Mike Rapoport
2026-10-01 3:17 ` Anshuman Khandual
2026-09-28 14:03 ` Dave Hansen
2026-09-30 9:54 ` David Hildenbrand (Arm)
2026-10-01 3:43 ` Anshuman Khandual
2026-11-01 22:16 ` patchwork-bot+linux-riscv [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=179357140534.2624073.9989407542230376185.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=borntraeger@linux.ibm.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=chleroy@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=liam@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ljs@kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mark.rutland@arm.com \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=ritesh.list@gmail.com \
--cc=rppt@kernel.org \
--cc=sshegde@linux.ibm.com \
--cc=surenb@google.com \
--cc=svens@linux.ibm.com \
--cc=tglx@kernel.org \
--cc=vbabka@kernel.org \
--cc=will@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