mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: Xiaofeng Yuan <xiaofengmian@163.com>, Nam Cao <namcao@linutronix.de>
Cc: Klara Modin <klara@kasm.eu>,
	prabhakar.csengg@gmail.com,  Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	 Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	 linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] riscv: patch: skip fixmap mapping when kernel text is already writable
Date: Thu, 13 Aug 2026 23:55:35 -0600 (MDT)	[thread overview]
Message-ID: <d8d4f892-ab9f-3baf-52aa-f269efc08ffd@kernel.org> (raw)
In-Reply-To: <8733wjzvkj.fsf@yellow.woof>

On Wed, 12 Aug 2026, Nam Cao wrote:

> Klara Modin <klara@kasm.eu> writes:
> > I have MODULES disabled and thus also STRICT_MODULE_RWX disabled, but
> > still STRICT_KERNEL_RWX enabled. I saw that an earlier version of this
> > patch[1] instead gated the first branch behind STRICT_KERNEL_RWX. That
> > version works fine for me.
> 
> Urgh, I got confused between STRICT_MODULE_RWX and STRICT_KERNEL_RWX, I
> suggested the final version.
> 
> Xiaofeng, can you send a patch?

Just dropped it from riscv/for-next, so, no need to send a revert.  
Xiaofeng, could you send an updated patch?

Thanks to Klara and Prabhakar for reporting the failures promptly!


- Paul

  reply	other threads:[~2026-08-14  5:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20  3:22 [PATCH v4 0/2] riscv: fix kprobes on minimal kernel configs Xiaofeng Yuan
2026-07-20  3:22 ` [PATCH v4 1/2] riscv: mm: make EXECMEM_KPROBES writable without CONFIG_STRICT_MODULE_RWX Xiaofeng Yuan
2026-07-20  3:22 ` [PATCH v4 2/2] riscv: patch: skip fixmap mapping when kernel text is already writable Xiaofeng Yuan
2026-08-11 20:39   ` Klara Modin
2026-08-12  6:45     ` Nam Cao
2026-08-14  5:55       ` Paul Walmsley [this message]
2026-08-13 14:14   ` Lad, Prabhakar
2026-07-20  7:11 ` [PATCH v4 0/2] riscv: fix kprobes on minimal kernel configs Nam Cao
2026-08-07  2:01 ` Paul Walmsley

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=d8d4f892-ab9f-3baf-52aa-f269efc08ffd@kernel.org \
    --to=pjw@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=klara@kasm.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=namcao@linutronix.de \
    --cc=palmer@dabbelt.com \
    --cc=prabhakar.csengg@gmail.com \
    --cc=xiaofengmian@163.com \
    /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
all inboxes | Powered by JetHome®