All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nam Cao <namcao@linutronix.de>
To: Klara Modin <klara@kasm.eu>, Xiaofeng Yuan <xiaofengmian@163.com>
Cc: 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: Wed, 12 Aug 2026 08:45:00 +0200	[thread overview]
Message-ID: <8733wjzvkj.fsf@yellow.woof> (raw)
In-Reply-To: <ant_8TaBbov_GS4i@soda.int.kasm.eu>

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?

Nam

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Nam Cao <namcao@linutronix.de>
To: Klara Modin <klara@kasm.eu>, Xiaofeng Yuan <xiaofengmian@163.com>
Cc: 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: Wed, 12 Aug 2026 08:45:00 +0200	[thread overview]
Message-ID: <8733wjzvkj.fsf@yellow.woof> (raw)
In-Reply-To: <ant_8TaBbov_GS4i@soda.int.kasm.eu>

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?

Nam

  reply	other threads:[~2026-08-12  6:45 UTC|newest]

Thread overview: 14+ 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 ` 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   ` 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-07-20  3:22   ` Xiaofeng Yuan
2026-08-11 20:39   ` Klara Modin
2026-08-11 20:39     ` Klara Modin
2026-08-12  6:45     ` Nam Cao [this message]
2026-08-12  6:45       ` Nam Cao
2026-07-20  7:11 ` [PATCH v4 0/2] riscv: fix kprobes on minimal kernel configs Nam Cao
2026-07-20  7:11   ` Nam Cao
2026-08-07  2:01 ` Paul Walmsley
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=8733wjzvkj.fsf@yellow.woof \
    --to=namcao@linutronix.de \
    --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=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --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 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.