Comment # 5 on bug 1216841 from WEI GAO

(In reply to Takashi Iwai from comment #1)
> What does this failure mean, more exactly?

The test code try to call fanotify_init with flags=FAN_REPORT_DFID_NAME_TARGET, 
event_f_flags=O_RDONLY on ext2 filesystem, the system call failed, return 
errno code is not ENOSYS or EINVAL but EXDEV. 
The test logic think EXDEV error code is unexpected.

test log:
tst_test.c:1650: TINFO: === Testing on ext2 ===
tst_test.c:1105: TINFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
mke2fs 1.47.0 (5-Feb-2023)
tst_test.c:1119: TINFO: Mounting /dev/loop0 to /tmp/LTP_fanSw9CmB/fs_mnt
fstyp=ext2 flags=0
fanotify.h:168: TBROK: fanotify_mark (3, FAN_MARK_ADD, ..., AT_FDCWD, ".")
failed: EXDEV (18)<<<<

test case code:
fanotify_init_flags_supported_on_fs(FAN_REPORT_DFID_NAME_TARGET, MOUNT_PATH);

static inline int fanotify_init_flags_supported_on_fs(unsigned int flags, const
char *fname)
{
        int fd;
        int rval = 0;

        fd = fanotify_init(flags, O_RDONLY);

        if (fd < 0) {
                if (errno == ENOSYS)
                        tst_brk(TCONF, "fanotify not configured in kernel");

                if (errno == EINVAL)
                        return -1;

                tst_brk(TBROK | TERRNO, "fanotify_init() failed");  <<<<<<
        }


BTW: i suppose 15sp6 use following build link? 
https://build.suse.de/package/show/Devel:Kernel:SLE15-SP6/kernel-default