ltp.lists.linux.it archive mirror
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] LTP release preparations
Date: Wed, 3 May 2023 18:32:39 +0200	[thread overview]
Message-ID: <20230503163239.GA3762958@pevik> (raw)
In-Reply-To: <ZFIq0CnSCS0jp8dE@rei>

> Hi!
> > * nfs08.sh: Skip on vfat
> > https://patchwork.ozlabs.org/project/ltp/patch/20230502151348.3677809-1-pvorel@suse.cz/

> This is workaround for bugs found by the "run nfs on all fs" patch,
> right?

Well, this is the problem which was found by this patchset. If you use TMPDIR
with vfat or exfat (unlikely, I know) on current master, it will fail.
I tested it on both loop device (demonstrated below) and on separate disc in VM.

dd if=/dev/zero of=/tmp/dev bs=1M count=500
losetup /dev/loop0 /tmp/dev
mkfs.exfat /dev/loop0
mkdir -p /export
mount /dev/loop0 /export
df -hT /export/
Filesystem     Type  Size  Used Avail Use% Mounted on
/dev/loop0     vfat  500M     0  500M   0% /export

PATH="/opt/ltp/testcases/bin:$PATH" TMPDIR=/export nfs08.sh -v 4 -t tcp
...
nfs08 1 TINFO: timeout per run is 0h 5m 0s
nfs08 1 TINFO: mount.nfs: (linux nfs-utils 2.6.3)
nfs08 1 TINFO: setup NFSv4, socket type tcp
nfs08 1 TINFO: Mounting NFS: mount -v -t nfs -o proto=tcp,vers=4 10.0.0.2:/export/LTP_nfs08.R9JOL8zozk/4/tcp /export/LTP_nfs08.R9JOL8zozk/4/0
nfs08 1 TINFO: testing NFS cache invalidation for directories
1
nfs08 1 TPASS: ls | grep 1 passed as expected
nfs08 1 TFAIL: ls | grep 2 failed unexpectedly

Actually, nfs08.sh not working on vfat and exfat
=> therefore nfs_lib.sh should be without TST_SKIP_FILESYSTEMS (currently all tests whitelists exfat)
and nfs08.sh should have: TST_SKIP_FILESYSTEMS="exfat,vfat"

umount /export
umount: /export: target is busy.

fuser -vm /dev/loop0
                     USER        PID ACCESS COMMAND
/dev/loop0:          root     kernel mount /export
                     root     kernel knfsd /export

=> Forced me to umount with -l or reboot, regardless used filesystem on
/dev/loop0.  This is fixed in this patchset which uses TST_ALL_FILESYSTEMS,
but I'd prefer to merge it instead of fixing master.

This is reproducible even if I just add new device (i.e. not a loop device) to VM.

> I suppose that it may be better not to enable nfs on all filesystems for
> this release so that we have time to figure out what is wrong before
> next release.

> I really do not like applying "temporary" workarounds for real bugs in
> the LTP codebase. There is always danger of "temporary" being forgotten
> and we end up masking the real bug for eternity.

We're masking the problems, because by default we test on what's on /tmp
(often tmpfs, which is unlikely to be used for NFS or ext4 or btrfs).

I need to test more old distros, I suspect that nfs-utils 1.3.3 has problems
with vfat, exfat, tmpfs and fuse, which is in Debian 11 (bullseye).

=> Maybe, as a start we could decide to run nfs_lib.sh only on modern linux
filesystems: i.e. btrfs, ext4, xfs
We could have:
TST_SKIP_FILESYSTEMS="btrfs,exfat,ext2,ext3,fuse,ntfs,vfat,tmpfs"
That would shorten the runtime and have more test coverage.
WDYT? I'm about to send v5 and run tests in the loop. Shell I include this
change?

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2023-05-03 16:32 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26  9:17 [LTP] LTP release preparations Cyril Hrubis
2023-04-26 10:01 ` Li Wang
2023-04-26 10:08   ` Li Wang
2023-05-08 12:31   ` Li Wang
2023-05-09  9:29     ` Cyril Hrubis
2023-05-10  6:39       ` Li Wang
2023-05-10 13:03         ` Petr Vorel
2023-05-11  5:48           ` Li Wang
2023-05-15 13:15           ` Cyril Hrubis
2023-05-16  4:58             ` Petr Vorel
2023-05-16  5:35               ` Petr Vorel
2023-05-16  5:46                 ` Petr Vorel
2023-04-26 10:07 ` Teo Couprie Diaz
2023-04-27 14:06 ` Andrea Cervesato via ltp
2023-04-28  9:12 ` Yang Xu (Fujitsu)
2023-05-02 12:18   ` Cyril Hrubis
2023-05-08  5:27     ` Yang Xu (Fujitsu)
2023-05-02 14:37 ` Petr Vorel
2023-05-02 15:14   ` Petr Vorel
2023-05-03  9:35     ` Cyril Hrubis
2023-05-03 16:32       ` Petr Vorel [this message]
2023-05-04 10:28         ` Petr Vorel
2023-05-03  9:31   ` Cyril Hrubis
2023-05-03 12:56     ` Petr Vorel
2023-05-04 13:17     ` Petr Vorel
2023-05-04 13:44       ` Cyril Hrubis
2023-05-04 20:37         ` Petr Vorel
2023-05-05 16:55 ` Petr Vorel
2023-05-10 12:59 ` Martin Doucha
2023-05-10 13:15   ` Cyril Hrubis
  -- strict thread matches above, loose matches on Subject: below --
2024-01-02 12:53 [LTP] LTP Release preparations Cyril Hrubis
2024-01-02 21:01 ` Petr Vorel
2024-01-10 18:06   ` Petr Vorel
2024-01-11 10:28     ` Petr Vorel
2024-01-03  1:57 ` Petr Vorel
2024-01-03  8:43 ` Yang Xu (Fujitsu)
2024-01-04 12:26 ` Petr Vorel
2024-01-04 12:35   ` Cyril Hrubis
2024-01-18 14:44 ` Cyril Hrubis
2024-01-25 10:17   ` Li Wang
2024-01-25 11:04     ` Cyril Hrubis
2024-01-26 10:40       ` Li Wang
2023-09-13  8:56 Cyril Hrubis
2023-09-13  9:45 ` Martin Doucha
2023-09-13  9:53 ` Andrea Cervesato via ltp
2023-09-13 11:18   ` Cyril Hrubis
2023-09-15  7:07 ` Petr Vorel
2023-09-15 12:03   ` Petr Vorel
2023-09-15 13:46     ` Petr Vorel
2023-09-15 13:02 ` Andrea Cervesato via ltp
2023-09-15 14:01   ` Cyril Hrubis
2023-09-18 11:23 ` Petr Vorel
2023-09-19  9:33   ` Richard Palethorpe
2023-09-26 10:50 ` Petr Vorel
2023-09-28  7:44   ` Li Wang
2023-09-28 17:39     ` Petr Vorel
2023-09-30  0:11   ` Edward Liaw via ltp
2023-09-30  6:22     ` Petr Vorel
2022-05-09 12:50 [LTP] LTP release preparations Cyril Hrubis
2022-05-09 13:51 ` Petr Vorel
2022-05-10  8:36 ` Li Wang
2022-05-10 13:54   ` Cyril Hrubis
2022-05-19 11:42 ` Martin Doucha
2022-05-19 12:11   ` Cyril Hrubis
2022-05-24 13:01 ` Cyril Hrubis
2022-01-05 11:36 [LTP] LTP Release preparations Cyril Hrubis
2022-01-05 14:45 ` Amir Goldstein
2022-01-05 14:53   ` Cyril Hrubis
2022-01-05 16:57     ` Petr Vorel
2022-01-06  9:52 ` xuyang2018.jy
2022-01-07  9:06 ` Li Wang
2022-01-07  9:51   ` Cyril Hrubis
2022-01-14  9:47 ` Cyril Hrubis
2018-04-12 11:35 Cyril Hrubis
2018-04-19 14:17 ` Cyril Hrubis
2018-04-20  3:56   ` Li Wang
2018-04-20 10:49   ` Petr Vorel
2018-04-24 13:39   ` Cyril Hrubis
2018-04-24 21:08     ` Jan Stancek
2018-04-25 13:23       ` Cyril Hrubis
2018-04-25 13:42         ` Jan Stancek
2018-04-25 13:44           ` Cyril Hrubis
2018-04-25 14:11     ` Petr Vorel
2018-05-03  9:28     ` Cyril Hrubis
2018-05-03 11:41       ` Alexey Kodanev
2018-05-03 12:06       ` Petr Vorel
2018-05-11 12:17       ` Cyril Hrubis
2016-01-05 15:36 [LTP] LTP release preparations 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=20230503163239.GA3762958@pevik \
    --to=pvorel@suse.cz \
    --cc=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;
as well as URLs for NNTP newsgroup(s).