From: Christian Brauner <brauner@kernel.org>
To: linux-fsdevel@vger.kernel.org, Jann Horn <jannh@google.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: "Eric Dumazet" <edumazet@google.com>,
"Oleg Nesterov" <oleg@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Daan De Meyer" <daan.j.demeyer@gmail.com>,
"David Rheinsberg" <david@readahead.eu>,
"Jakub Kicinski" <kuba@kernel.org>, "Jan Kara" <jack@suse.cz>,
"Lennart Poettering" <lennart@poettering.net>,
"Luca Boccassi" <bluca@debian.org>, "Mike Yuan" <me@yhndnzj.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-security-module@vger.kernel.org,
"Christian Brauner" <brauner@kernel.org>,
"Alexander Mikhalitsyn" <alexander@mihalicyn.com>
Subject: [PATCH v5 6/9] coredump: show supported coredump modes
Date: Fri, 09 May 2025 12:25:38 +0200 [thread overview]
Message-ID: <20250509-work-coredump-socket-v5-6-23c5b14df1bc@kernel.org> (raw)
In-Reply-To: <20250509-work-coredump-socket-v5-0-23c5b14df1bc@kernel.org>
Allow userspace to discover what coredump modes are supported.
Signed-off-by: Christian Brauner <brauner@kernel.org>
---
fs/coredump.c | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/fs/coredump.c b/fs/coredump.c
index ff42688ec9ac..fa50a681b225 100644
--- a/fs/coredump.c
+++ b/fs/coredump.c
@@ -1263,6 +1263,12 @@ static int proc_dostring_coredump(const struct ctl_table *table, int write,
static const unsigned int core_file_note_size_min = CORE_FILE_NOTE_SIZE_DEFAULT;
static const unsigned int core_file_note_size_max = CORE_FILE_NOTE_SIZE_MAX;
+static char core_modes[] = {
+ "file\npipe"
+#ifdef CONFIG_UNIX
+ "\nlinuxafsk/coredump.socket"
+#endif
+};
static const struct ctl_table coredump_sysctls[] = {
{
@@ -1306,6 +1312,13 @@ static const struct ctl_table coredump_sysctls[] = {
.extra1 = SYSCTL_ZERO,
.extra2 = SYSCTL_ONE,
},
+ {
+ .procname = "core_modes",
+ .data = core_modes,
+ .maxlen = sizeof(core_modes) - 1,
+ .mode = 0444,
+ .proc_handler = proc_dostring,
+ },
};
static int __init init_fs_coredump_sysctls(void)
--
2.47.2
next prev parent reply other threads:[~2025-05-09 10:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 10:25 [PATCH v5 0/9] coredump: add coredump socket Christian Brauner
2025-05-09 10:25 ` [PATCH v5 1/9] coredump: massage format_corname() Christian Brauner
2025-05-09 15:46 ` Alexander Mikhalitsyn
2025-05-09 10:25 ` [PATCH v5 2/9] coredump: massage do_coredump() Christian Brauner
2025-05-09 16:30 ` Alexander Mikhalitsyn
2025-05-09 10:25 ` [PATCH v5 3/9] coredump: reflow dump helpers a little Christian Brauner
2025-05-09 16:36 ` Alexander Mikhalitsyn
2025-05-09 10:25 ` [PATCH v5 4/9] coredump: add coredump socket Christian Brauner
2025-05-09 15:40 ` Christian Brauner
2025-05-09 16:40 ` Luca Boccassi
2025-05-09 17:30 ` Kuniyuki Iwashima
2025-05-09 10:25 ` [PATCH v5 5/9] pidfs, coredump: add PIDFD_INFO_COREDUMP Christian Brauner
2025-05-09 10:25 ` Christian Brauner [this message]
2025-05-09 10:25 ` [PATCH v5 7/9] coredump: validate socket name as it is written Christian Brauner
2025-05-09 10:25 ` [PATCH v5 8/9] selftests/pidfd: add PIDFD_INFO_COREDUMP infrastructure Christian Brauner
2025-05-09 10:25 ` [PATCH v5 9/9] selftests/coredump: add tests for AF_UNIX coredumps Christian Brauner
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=20250509-work-coredump-socket-v5-6-23c5b14df1bc@kernel.org \
--to=brauner@kernel.org \
--cc=alexander@mihalicyn.com \
--cc=bluca@debian.org \
--cc=daan.j.demeyer@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=david@readahead.eu \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=lennart@poettering.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=me@yhndnzj.com \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pabeni@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=zbyszek@in.waw.pl \
/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;
as well as URLs for NNTP newsgroup(s).