From: Kees Cook <kees@kernel.org>
To: Svetlana Parfenova <svetlana.parfenova@syntacore.com>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.f, viro@zeniv.linux.org.uk,
brauner@kernel.org, jack@suse.cz, akpm@linux-foundation.org,
david@redhat.com, lorenzo.stoakes@oracle.com,
Liam.Howlett@oracle.com, vbabka@suse.cz, rppt@kernel.org,
surenb@google.com, mhocko@suse.com
Subject: Re: [RFC RESEND v3] binfmt_elf: preserve original ELF e_flags for core dumps
Date: Wed, 3 Sep 2025 20:52:02 -0700 [thread overview]
Message-ID: <202509032051.BF7FC654F@keescook> (raw)
In-Reply-To: <20250901135350.619485-1-svetlana.parfenova@syntacore.com>
On Mon, Sep 01, 2025 at 08:53:50PM +0700, Svetlana Parfenova wrote:
> diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
> index a4b233a0659e..1bef00208bdd 100644
> --- a/arch/riscv/Kconfig
> +++ b/arch/riscv/Kconfig
> @@ -224,6 +224,7 @@ config RISCV
> select VDSO_GETRANDOM if HAVE_GENERIC_VDSO
> select USER_STACKTRACE_SUPPORT
> select ZONE_DMA32 if 64BIT
> + select ARCH_HAS_ELF_CORE_EFLAGS
>
> config RUSTC_SUPPORTS_RISCV
I'll take this patch and alphabetize the above select into the right
place. Everything else looks great. Thank you!
-Kees
--
Kees Cook
next prev parent reply other threads:[~2025-09-04 3:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 16:18 [RFC RESEND] binfmt_elf: preserve original ELF e_flags in " Svetlana Parfenova
2025-08-06 18:57 ` Kees Cook
2025-08-07 13:13 ` Svetlana Parfenova
2025-08-07 21:14 ` Kees Cook
2025-08-08 15:54 ` Svetlana Parfenova
2025-08-08 21:54 ` Kees Cook
2025-08-11 9:53 ` [RFC RESEND v2] binfmt_elf: preserve original ELF e_flags for " Svetlana Parfenova
2025-08-25 17:17 ` Kees Cook
2025-09-01 13:58 ` Svetlana Parfenova
2025-09-01 13:53 ` [RFC RESEND v3] " Svetlana Parfenova
2025-09-04 3:52 ` Kees Cook [this message]
2025-09-04 3:52 ` Kees Cook
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=202509032051.BF7FC654F@keescook \
--to=kees@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.f \
--cc=aou@eecs.berkeley.edu \
--cc=brauner@kernel.org \
--cc=david@redhat.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=svetlana.parfenova@syntacore.com \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
/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