[LTP] [PATCH v2 2/3] Add fanotify_get_supported_init_flags() helper function
Martin Doucha
mdoucha@suse.cz
Mon Oct 24 16:58:11 CEST 2022
On 24. 10. 22 16:34, Amir Goldstein wrote:
> This is how I would fix the problem:
>
> <snip>
>
> Give or take using more macros and your nicer flag prints.
> There is no need for auto-detection of the unsupported kernel flags.
>
> If the test case is expected to get to fanotify_mark() (i.e. non-zero tc->mask)
> EINVAL from fanotify_init() always means "unsupported".
This would be a good approach if fanotify_init() returned distinct error
code for "flag not implemented", like ENOTSUP. But when EINVAL is
returned for both "not implemented" and "wrong use", this has a risk of
hiding real bugs. That's why I'm trying to detect the actual set of
flags implemented in the running kernel before running the real tests.
And since some flags may be backported to older kernels, generating
feature sets based on kernel version is not a solution.
--
Martin Doucha mdoucha@suse.cz
QA Engineer for Software Maintenance
SUSE LINUX, s.r.o.
CORSO IIa
Krizikova 148/34
186 00 Prague 8
Czech Republic
More information about the ltp
mailing list