From: Petr Vorel <petr.vorel@gmail.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/1] msgrcv/msgrcv08.c: Use struct msgbuf defined in <sys/msg.h>
Date: Wed, 20 Mar 2019 22:57:07 +0100 [thread overview]
Message-ID: <20190320215707.30268-1-petr.vorel@gmail.com> (raw)
which requires to define _GNU_SOURCE.
This fixes MUSL build.
NOTE: char array from struct has usually length 1, the one from test had 16,
but that's not a limitation.
Fixes: eccd238da ("ipc/msgrcv: add new testcase msgrcv08")
Reported-by: Dengke Du <dengke.du@windriver.com>
Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
---
Hi Li,
what was the reason to use size 16?
Kind regards,
Petr
PS: I found and fix this error independently while working on MUSL build
fixes, but than found it was reported by Dengke Du in PR #177 [1].
[1] https://github.com/linux-test-project/ltp/pull/177/commits/87c4a4ae2817f835a594ab795dc938a27c642b92
---
testcases/kernel/syscalls/ipc/msgrcv/msgrcv08.c | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/testcases/kernel/syscalls/ipc/msgrcv/msgrcv08.c b/testcases/kernel/syscalls/ipc/msgrcv/msgrcv08.c
index a757c0d18..21d77c9dd 100644
--- a/testcases/kernel/syscalls/ipc/msgrcv/msgrcv08.c
+++ b/testcases/kernel/syscalls/ipc/msgrcv/msgrcv08.c
@@ -35,6 +35,7 @@
* If this progarm is compiled as 64-bit application it works.
*/
+#define _GNU_SOURCE
#include <stdio.h>
#include <string.h>
#include <unistd.h>
@@ -48,11 +49,6 @@ const int TST_TOTAL = 1;
#if __WORDSIZE == 32
-struct msgbuf {
- long mtype; /* message type, must be > 0 */
- char mtext[16]; /* message data */
-};
-
static void msr(int msqid)
{
struct msgbuf msbs;
--
2.21.0
next reply other threads:[~2019-03-20 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 21:57 Petr Vorel [this message]
2019-03-21 9:51 ` [LTP] [PATCH 1/1] msgrcv/msgrcv08.c: Use struct msgbuf defined in <sys/msg.h> Cyril Hrubis
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=20190320215707.30268-1-petr.vorel@gmail.com \
--to=petr.vorel@gmail.com \
--cc=ltp@lists.linux.it \
/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