From: UYeol Jo <jouyeol8739@gmail.com>
To: Shuah Khan <shuah@kernel.org>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
richard.weiyang@gmail.com, akpm@linux-foundation.org,
sef1548@gmail.com, jouyeol8739@gmail.com
Subject: [PATCH] selftests/ipc: skip msgque test if MSG_COPY is not supported
Date: Mon, 19 Jan 2026 20:21:20 +0900 [thread overview]
Message-ID: <20260119112120.83592-1-jouyeol8739@gmail.com> (raw)
The msgque test uses the MSG_COPY flag, which depends on
CONFIG_CHECKPOINT_RESTORE. On kernels where this option is disabled,
msgrcv() fails with ENOSYS.
Currently, the test reports this as a failure:
Change it to skip the test instead, as the failure is due to missing
kernel configuration rather than a bug in the IPC subsystem.
# selftests: ipc: msgque
# not ok 1 Failed to copy IPC message: Function not implemented (38)
# not ok 2 Failed to dump queue: -38
After this patch, the test reports a skip instead of failure:
1..0 # SKIP MSG_COPY not supported
Signed-off-by: UYeol Jo <jouyeol8739@gmail.com>
---
tools/testing/selftests/ipc/msgque.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tools/testing/selftests/ipc/msgque.c b/tools/testing/selftests/ipc/msgque.c
index e107379d185c..82f73cdae120 100644
--- a/tools/testing/selftests/ipc/msgque.c
+++ b/tools/testing/selftests/ipc/msgque.c
@@ -161,6 +161,9 @@ int dump_queue(struct msgque_data *msgque)
ret = msgrcv(msgque->msq_id, &msgque->messages[i].mtype,
MAX_MSG_SIZE, i, IPC_NOWAIT | MSG_COPY);
if (ret < 0) {
+ if (errno == ENOSYS)
+ ksft_exit_skip("MSG_COPY not supported\n");
+
ksft_test_result_fail("Failed to copy IPC message: %m (%d)\n", errno);
return -errno;
}
--
2.43.0
next reply other threads:[~2026-01-19 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 11:21 UYeol Jo [this message]
2026-01-21 0:03 ` Shuah
2026-01-24 8:35 ` 조우열
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=20260119112120.83592-1-jouyeol8739@gmail.com \
--to=jouyeol8739@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=richard.weiyang@gmail.com \
--cc=sef1548@gmail.com \
--cc=shuah@kernel.org \
/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
all inboxes | Powered by JetHome®