From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Cc: Gabriel Krisman Bertazi <krisman@collabora.com>,
Richard Palethorpe <rpalethorpe@suse.com>
Subject: Re: [LTP] [PATCH 1/1] fanotify.h: Include <linux/types.h>
Date: Thu, 26 Jan 2023 00:28:52 +0100 [thread overview]
Message-ID: <Y9G7NK0ptEIUliA3@pevik> (raw)
In-Reply-To: <20230125232751.31809-1-pvorel@suse.cz>
Hi,
Cc Jan, which replied to my question in private mail.
Kind regards,
Petr
> to add kernel types (__s32, __u32, ...).
> This fixes build on various Buildroot toolchains:
> In file included from fanotify.h:14,
> from fanotify04.c:25:
> ../../../../include/lapi/fanotify.h:198:2: error: unknown type name ‘__s32’
> 198 | __s32 error;
> | ^~~~~
> ../../../../include/lapi/fanotify.h:199:2: error: unknown type name ‘__u32’
> 199 | __u32 error_count;
> | ^~~~~
> NOTE: Historically we tried to minimize number of linux includes,
> because it would often lead to broken builds. Headers got better over
> time and LTP also dropped support for archaic kernels over time.
> Therefore we can keep original kernel types here.
> Fixes: 67069fc46a ("syscalls/fanotify22: Validate the generic error info")
> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
> ---
> testcases/kernel/syscalls/fanotify/fanotify.h | 1 +
> 1 file changed, 1 insertion(+)
> diff --git a/testcases/kernel/syscalls/fanotify/fanotify.h b/testcases/kernel/syscalls/fanotify/fanotify.h
> index 51078103eb..da78788378 100644
> --- a/testcases/kernel/syscalls/fanotify/fanotify.h
> +++ b/testcases/kernel/syscalls/fanotify/fanotify.h
> @@ -11,6 +11,7 @@
> #include <sys/types.h>
> #include <sys/stat.h>
> #include <errno.h>
> +#include <linux/types.h>
> #include "lapi/fanotify.h"
> #include "lapi/fcntl.h"
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-01-25 23:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 23:27 [LTP] [PATCH 1/1] fanotify.h: Include <linux/types.h> Petr Vorel
2023-01-25 23:28 ` Petr Vorel [this message]
2023-01-26 10:26 ` Cyril Hrubis
2023-01-26 10:39 ` Petr Vorel
2023-01-26 10:49 ` Petr Vorel
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=Y9G7NK0ptEIUliA3@pevik \
--to=pvorel@suse.cz \
--cc=krisman@collabora.com \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.com \
/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