From: Jeff Layton <jlayton@kernel.org>
To: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, Jann Horn <jannh@google.com>
Cc: "Josef Bacik" <josef@toxicpanda.com>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Daan De Meyer" <daan.j.demeyer@gmail.com>,
"Jan Kara" <jack@suse.cz>,
"Lennart Poettering" <lennart@poettering.net>,
"Mike Yuan" <me@yhndnzj.com>,
"Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>,
"Alexander Mikhalitsyn" <alexander@mihalicyn.com>
Subject: Re: [PATCH 2/5] selftests/coredump: fix build
Date: Mon, 09 Jun 2025 10:17:25 -0400 [thread overview]
Message-ID: <4352cf30f1a599b67b550c0eaac443231cf28c54.camel@kernel.org> (raw)
In-Reply-To: <20250530-work-coredump-socket-protocol-v1-2-20bde1cd4faa@kernel.org>
On Fri, 2025-05-30 at 13:10 +0200, Christian Brauner wrote:
> Fix various warnings in the selftest build.
>
> Signed-off-by: Christian Brauner <brauner@kernel.org>
> ---
> tools/testing/selftests/coredump/Makefile | 2 +-
> tools/testing/selftests/coredump/stackdump_test.c | 17 +++++------------
> 2 files changed, 6 insertions(+), 13 deletions(-)
>
> diff --git a/tools/testing/selftests/coredump/Makefile b/tools/testing/selftests/coredump/Makefile
> index ed210037b29d..bc287a85b825 100644
> --- a/tools/testing/selftests/coredump/Makefile
> +++ b/tools/testing/selftests/coredump/Makefile
> @@ -1,5 +1,5 @@
> # SPDX-License-Identifier: GPL-2.0-only
> -CFLAGS = $(KHDR_INCLUDES)
> +CFLAGS = -Wall -O0 $(KHDR_INCLUDES)
>
> TEST_GEN_PROGS := stackdump_test
> TEST_FILES := stackdump
> diff --git a/tools/testing/selftests/coredump/stackdump_test.c b/tools/testing/selftests/coredump/stackdump_test.c
> index 9984413be9f0..aa366e6f13a7 100644
> --- a/tools/testing/selftests/coredump/stackdump_test.c
> +++ b/tools/testing/selftests/coredump/stackdump_test.c
> @@ -24,6 +24,8 @@ static void *do_nothing(void *)
> {
> while (1)
> pause();
> +
> + return NULL;
> }
>
> static void crashing_child(void)
> @@ -46,9 +48,7 @@ FIXTURE(coredump)
>
> FIXTURE_SETUP(coredump)
> {
> - char buf[PATH_MAX];
> FILE *file;
> - char *dir;
> int ret;
>
> self->pid_coredump_server = -ESRCH;
> @@ -106,7 +106,6 @@ FIXTURE_TEARDOWN(coredump)
>
> TEST_F_TIMEOUT(coredump, stackdump, 120)
> {
> - struct sigaction action = {};
> unsigned long long stack;
> char *test_dir, *line;
> size_t line_length;
> @@ -171,11 +170,10 @@ TEST_F_TIMEOUT(coredump, stackdump, 120)
>
> TEST_F(coredump, socket)
> {
> - int fd, pidfd, ret, status;
> + int pidfd, ret, status;
> FILE *file;
> pid_t pid, pid_coredump_server;
> struct stat st;
> - char core_file[PATH_MAX];
> struct pidfd_info info = {};
> int ipc_sockets[2];
> char c;
> @@ -356,11 +354,10 @@ TEST_F(coredump, socket)
>
> TEST_F(coredump, socket_detect_userspace_client)
> {
> - int fd, pidfd, ret, status;
> + int pidfd, ret, status;
> FILE *file;
> pid_t pid, pid_coredump_server;
> struct stat st;
> - char core_file[PATH_MAX];
> struct pidfd_info info = {};
> int ipc_sockets[2];
> char c;
> @@ -384,7 +381,7 @@ TEST_F(coredump, socket_detect_userspace_client)
> pid_coredump_server = fork();
> ASSERT_GE(pid_coredump_server, 0);
> if (pid_coredump_server == 0) {
> - int fd_server, fd_coredump, fd_peer_pidfd, fd_core_file;
> + int fd_server, fd_coredump, fd_peer_pidfd;
> socklen_t fd_peer_pidfd_len;
>
> close(ipc_sockets[0]);
> @@ -464,7 +461,6 @@ TEST_F(coredump, socket_detect_userspace_client)
> close(fd_coredump);
> close(fd_server);
> close(fd_peer_pidfd);
> - close(fd_core_file);
> _exit(EXIT_SUCCESS);
> }
> self->pid_coredump_server = pid_coredump_server;
> @@ -488,7 +484,6 @@ TEST_F(coredump, socket_detect_userspace_client)
> if (ret < 0)
> _exit(EXIT_FAILURE);
>
> - (void *)write(fd_socket, &(char){ 0 }, 1);
> close(fd_socket);
> _exit(EXIT_SUCCESS);
> }
> @@ -519,7 +514,6 @@ TEST_F(coredump, socket_enoent)
> int pidfd, ret, status;
> FILE *file;
> pid_t pid;
> - char core_file[PATH_MAX];
>
> file = fopen("/proc/sys/kernel/core_pattern", "w");
> ASSERT_NE(file, NULL);
> @@ -569,7 +563,6 @@ TEST_F(coredump, socket_no_listener)
> ASSERT_GE(pid_coredump_server, 0);
> if (pid_coredump_server == 0) {
> int fd_server;
> - socklen_t fd_peer_pidfd_len;
>
> close(ipc_sockets[0]);
>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2025-06-09 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 11:09 [PATCH 0/5] coredump: allow for flexible coredump handling Christian Brauner
2025-05-30 11:09 ` [PATCH 1/5] " Christian Brauner
2025-05-30 11:10 ` [PATCH 2/5] selftests/coredump: fix build Christian Brauner
2025-06-09 14:17 ` Jeff Layton [this message]
2025-05-30 11:10 ` [PATCH 3/5] selftests/coredump: cleanup coredump tests Christian Brauner
2025-05-30 11:10 ` [PATCH 4/5] tools: add coredump.h header Christian Brauner
2025-05-30 11:10 ` [PATCH 5/5] selftests/coredump: add coredump server selftests Christian Brauner
2025-06-09 14:19 ` [PATCH 0/5] coredump: allow for flexible coredump handling Jeff Layton
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=4352cf30f1a599b67b550c0eaac443231cf28c54.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=alexander@mihalicyn.com \
--cc=brauner@kernel.org \
--cc=daan.j.demeyer@gmail.com \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=josef@toxicpanda.com \
--cc=lennart@poettering.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=me@yhndnzj.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).