From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3 4/5] fanotify: Check FAN_REPORT_{FID, NAME} support
Date: Thu, 19 Nov 2020 11:30:45 +0100 [thread overview]
Message-ID: <20201119103045.GE2785@yuki.lan> (raw)
In-Reply-To: <20201113164944.26101-5-pvorel@suse.cz>
Hi!
> +int safe_fanotify_init(const char *file, const int lineno,
> + unsigned int flags, unsigned int event_f_flags)
> +{
> + int rval;
> +
> +#ifdef HAVE_SYS_FANOTIFY_H
> + rval = fanotify_init(flags, event_f_flags);
> +
> + if (rval == -1) {
> + if (errno == ENOSYS) {
> + tst_brk(TCONF, "%s:%d: fanotify is not configured in this kernel",
> + file, lineno);
> + }
> +
> + if (errno == EINVAL) {
> + if (flags & FAN_REPORT_FID) {
> + tst_brk(TCONF, "%s:%d: FAN_REPORT_FID not supported by kernel?",
> + file, lineno);
> + }
> +
> + if (flags & FAN_REPORT_NAME) {
> + tst_brk(TCONF, "%s:%d: FAN_REPORT_NAME not supported by kernel?",
> + file, lineno);
> + }
If we happen to have both in flags it will report only the first one
here. So maybe we should use tst_res(TINFO, "") followed by
tst_brk(TCONF, "Unsupported configuration, see above"); or something
like that.
> + }
> +
> + tst_brk(TBROK | TERRNO, "%s:%d: fanotify_init() failed",
> + file, lineno);
> + }
> +#else
> + tst_brk(TCONF, "Header <sys/fanotify.h> is not present");
> +#endif /* HAVE_SYS_FANOTIFY_H */
> +
> + return rval;
> +}
> +
> +#define SAFE_FANOTIFY_INIT(fan, mode) \
> + safe_fanotify_init(__FILE__, __LINE__, (fan), (mode))
> +
> static inline int safe_fanotify_mark(const char *file, const int lineno,
> int fd, unsigned int flags, uint64_t mask,
> int dfd, const char *pathname)
> --
> 2.29.2
>
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2020-11-19 10:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 16:49 [LTP] [PATCH v3 0/5] Introduce SAFE_FANOTIFY_MARK() macro + cleanup Petr Vorel
2020-11-13 16:49 ` [LTP] [PATCH v3 1/5] fanotify12: Drop incorrect hint Petr Vorel
2020-11-19 10:06 ` Cyril Hrubis
2020-11-13 16:49 ` [LTP] [PATCH v3 2/5] fanotify: Handle supported features checks in setup() Petr Vorel
2020-11-19 10:16 ` Cyril Hrubis
2020-11-25 16:56 ` Petr Vorel
2020-11-13 16:49 ` [LTP] [PATCH v3 3/5] fanotify: Introduce SAFE_FANOTIFY_MARK() macro Petr Vorel
2020-11-19 10:27 ` Cyril Hrubis
2020-11-19 10:54 ` Amir Goldstein
2020-11-25 14:16 ` Petr Vorel
2020-11-25 15:41 ` Amir Goldstein
2020-11-25 18:24 ` Petr Vorel
2020-11-25 19:55 ` Amir Goldstein
2020-11-25 20:25 ` Petr Vorel
2020-11-26 3:00 ` Amir Goldstein
2020-11-13 16:49 ` [LTP] [PATCH v3 4/5] fanotify: Check FAN_REPORT_{FID, NAME} support Petr Vorel
2020-11-19 10:30 ` Cyril Hrubis [this message]
2020-11-13 16:49 ` [LTP] [PATCH v3 5/5] fanotify: Add a pedantic check for return value Petr Vorel
2020-11-19 10:31 ` 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=20201119103045.GE2785@yuki.lan \
--to=chrubis@suse.cz \
--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