From: Petr Vorel <pvorel@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Jan Kara <jack@suse.cz>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] fanotify: Fix broken tests due to fanotify_events_supported_by_kernel()
Date: Tue, 28 Nov 2023 12:30:24 +0100 [thread overview]
Message-ID: <20231128113024.GA369141@pevik> (raw)
In-Reply-To: <CAOQ4uxgbHEpLz+pNONOMun5KFUrKnGZX=KbHPkx7LjN3Z4RuRg@mail.gmail.com>
Hi Amir,
...
> > > > FYI, in this branch:
> > > > https://github.com/amir73il/ltp/commits/fanotify_fsid
> > FYI the first commit breaks at least vfat on fanotify13
> > # LTP_SINGLE_FS_TYPE=vfat ./fanotify13
> > ...
> > tst_test.c:1650: TINFO: === Testing on vfat ===
> > tst_test.c:1105: TINFO: Formatting /dev/loop1 with vfat opts='' extra opts=''
> > tst_test.c:1119: TINFO: Mounting /dev/loop1 to /tmp/LTP_fanM9wLom/mntpoint fstyp=vfat flags=0
> > fanotify13.c:152: TINFO: Test #0.1: FAN_REPORT_FID with mark flag: FAN_MARK_INODE
> > fanotify13.c:157: TCONF: overlayfs not supported on vfat
> > fanotify13.c:152: TINFO: Test #1.1: FAN_REPORT_FID with mark flag: FAN_MARK_INODE
> > fanotify13.c:157: TCONF: overlayfs not supported on vfat
> > fanotify13.c:152: TINFO: Test #2.1: FAN_REPORT_FID with mark flag: FAN_MARK_MOUNT
> > fanotify13.c:157: TCONF: overlayfs not supported on vfat
> > fanotify13.c:152: TINFO: Test #3.1: FAN_REPORT_FID with mark flag: FAN_MARK_MOUNT
> > fanotify13.c:157: TCONF: overlayfs not supported on vfat
> > fanotify13.c:152: TINFO: Test #4.1: FAN_REPORT_FID with mark flag: FAN_MARK_FILESYSTEM
> > fanotify13.c:157: TCONF: overlayfs not supported on vfat
> > fanotify13.c:152: TINFO: Test #5.1: FAN_REPORT_FID with mark flag: FAN_MARK_FILESYSTEM
> > fanotify13.c:157: TCONF: overlayfs not supported on vfat
> > tst_device.c:408: TINFO: umount('mntpoint') failed with EBUSY, try 1...
> > tst_device.c:412: TINFO: Likely gvfsd-trash is probing newly mounted fs, kill it to speed up tests.
> > tst_device.c:408: TINFO: umount('mntpoint') failed with EBUSY, try 2...
> > tst_device.c:408: TINFO: umount('mntpoint') failed with EBUSY, try 3...
> > ...
> > tst_device.c:408: TINFO: umount('mntpoint') failed with EBUSY, try 50...
> > tst_device.c:419: TWARN: Failed to umount('mntpoint') after 50 retries
> > tst_test.c:1650: TINFO: === Testing on exfat ===
> > tst_test.c:1105: TINFO: Formatting /dev/loop1 with exfat opts='' extra opts=''
> > tst_test.c:1119: TINFO: Mounting /dev/loop1 to /tmp/LTP_fanM9wLom/mntpoint fstyp=exfat flags=0
> > tst_test.c:1119: TINFO: Trying FUSE...
> > FUSE exfat 1.4.0 (libfuse2)
> > fuse: mount failed: Device or resource busy
> > tst_test.c:1119: TBROK: mount.exfat failed with 256
> I believe this breakage is a regression due to overlayfs bug in v6.7-rc1
> that was fixed by commit
> 37f32f526438 ("ovl: fix memory leak in ovl_parse_param()") in v6.7-rc2.
Indeed, it works on openSUSE 6.7.0-rc3-3.ge7296f9-default.
Thanks for info.
Kind regards,
Petr
> Thanks,
> Amir.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2023-11-28 11:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 15:40 [LTP] [PATCH] fanotify: Fix broken tests due to fanotify_events_supported_by_kernel() Jan Kara
2023-11-27 16:22 ` Petr Vorel
2023-11-27 17:40 ` Amir Goldstein
2023-11-27 18:26 ` Jan Kara
2023-11-27 22:07 ` Petr Vorel
2023-11-28 11:14 ` Amir Goldstein
2023-11-28 11:30 ` Petr Vorel [this message]
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=20231128113024.GA369141@pevik \
--to=pvorel@suse.cz \
--cc=amir73il@gmail.com \
--cc=jack@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