From: Nam Cao <namcao@linutronix.de>
To: Xiaofeng Yuan <xiaofengmian@163.com>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>
Cc: Alexandre Ghiti <alex@ghiti.fr>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] riscv: mm: make EXECMEM_KPROBES writable without CONFIG_STRICT_MODULE_RWX
Date: Sun, 19 Jul 2026 20:38:19 +0200 [thread overview]
Message-ID: <87fr1ebzac.fsf@yellow.woof> (raw)
In-Reply-To: <20260719093024.33351-2-xiaofengmian@163.com>
Xiaofeng Yuan <xiaofengmian@163.com> writes:
> @@ -1457,7 +1457,9 @@ struct execmem_info __init *execmem_arch_setup(void)
> [EXECMEM_KPROBES] = {
> .start = VMALLOC_START,
> .end = VMALLOC_END,
> - .pgprot = PAGE_KERNEL_READ_EXEC,
> + .pgprot = IS_ENABLED(CONFIG_STRICT_MODULE_RWX) ?
> + PAGE_KERNEL_READ_EXEC :
> + PAGE_KERNEL_EXEC,
The indentation is messed up. It looked fine in v2.
Nam
WARNING: multiple messages have this Message-ID (diff)
From: Nam Cao <namcao@linutronix.de>
To: Xiaofeng Yuan <xiaofengmian@163.com>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>
Cc: Alexandre Ghiti <alex@ghiti.fr>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] riscv: mm: make EXECMEM_KPROBES writable without CONFIG_STRICT_MODULE_RWX
Date: Sun, 19 Jul 2026 20:38:19 +0200 [thread overview]
Message-ID: <87fr1ebzac.fsf@yellow.woof> (raw)
In-Reply-To: <20260719093024.33351-2-xiaofengmian@163.com>
Xiaofeng Yuan <xiaofengmian@163.com> writes:
> @@ -1457,7 +1457,9 @@ struct execmem_info __init *execmem_arch_setup(void)
> [EXECMEM_KPROBES] = {
> .start = VMALLOC_START,
> .end = VMALLOC_END,
> - .pgprot = PAGE_KERNEL_READ_EXEC,
> + .pgprot = IS_ENABLED(CONFIG_STRICT_MODULE_RWX) ?
> + PAGE_KERNEL_READ_EXEC :
> + PAGE_KERNEL_EXEC,
The indentation is messed up. It looked fine in v2.
Nam
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-07-19 18:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-19 9:30 [PATCH v3 0/2] riscv: fix kprobes on minimal kernel configs Xiaofeng Yuan
2026-07-19 9:30 ` Xiaofeng Yuan
2026-07-19 9:30 ` [PATCH v3 1/2] riscv: mm: make EXECMEM_KPROBES writable without CONFIG_STRICT_MODULE_RWX Xiaofeng Yuan
2026-07-19 9:30 ` Xiaofeng Yuan
2026-07-19 18:38 ` Nam Cao [this message]
2026-07-19 18:38 ` Nam Cao
2026-07-19 9:30 ` [PATCH v3 2/2] riscv: patch: skip fixmap mapping when kernel text is already writable Xiaofeng Yuan
2026-07-19 9:30 ` Xiaofeng Yuan
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=87fr1ebzac.fsf@yellow.woof \
--to=namcao@linutronix.de \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--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.