From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/4] libswap: add known swap supported fs check
Date: Mon, 22 Jan 2024 21:23:25 +0100 [thread overview]
Message-ID: <20240122202325.GA119341@pevik> (raw)
In-Reply-To: <CAEemH2cNn1kyWrnqXHHeOteGT_FQ=PBVc55NFhkZbmkbMOoD=A@mail.gmail.com>
Hi Li,
> Great, and FYI.
> I just pushed a new commit to resolve the FIBMAP (unsupported on BTRFS)
> problem on my ltp:libswap branch.
> https://github.com/wangli5665/ltp/commit/699711bfe8c8dbc3597c46587345fa1197c054c9
> Hope you can try on your side and give some feedback :).
Unfortunately regardless of kernel version it fails:
# LTP_SINGLE_FS_TYPE=btrfs ./swapon01
...
tst_test.c:1669: TINFO: === Testing on btrfs ===
tst_test.c:1117: TINFO: Formatting /dev/loop0 with btrfs opts='' extra opts=''
tst_test.c:1131: TINFO: Mounting /dev/loop0 to /tmp/LTP_swa497AKp/mntpoint fstyp=btrfs flags=0
tst_ioctl.c:21: TINFO: FIBMAP ioctl is NOT supported: EINVAL (22)
libswap.c:93: TINFO: File 'mntpoint/swapfile01' is not contiguous
libswap.c:34: TINFO: FS_NOCOW_FL attribute set on mntpoint/swapfile01
libswap.c:169: TFAIL: swapon() on btrfs failed: EINVAL (22)
Also, tst_brk() in is_swap_supported() causes test to fail quickly.
Given similar Martin's fix to shell API I merged today, which use tst_res +
return instead of tst_brk [1] I suggest to use tst_res + change return function
from void to int and handle another return in the test. That will allow to test
other filesystems (which is useful to see, if particular filesystem code is
broken or or VFS or some common code reused by all filesystems). This is the
reason why I don't think "quit as early as possible" is a good approach when
testing on all filesystems.
Kind regards,
Petr
[1] https://github.com/linux-test-project/ltp/commit/5c73ad84f3e6db9a965df3ed4a846352136ed990
> > > https://github.com/wangli5665/ltp/tree/libswap
> > > And, I prefer to wait for Cryil's feedback before posting them in ML:)
> > +1
> > Kind regards,
> > Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-01-22 20:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 7:29 [LTP] [PATCH 1/4] libswap: add known swap supported fs check Li Wang
2024-01-22 7:29 ` [LTP] [PATCH 2/4] swapon01: Test on all filesystems Li Wang
2024-01-22 7:29 ` [LTP] [PATCH 3/4] swapon01: Improving test with memory limits and swap reporting Li Wang
2024-01-22 9:08 ` Petr Vorel
2024-01-22 7:29 ` [LTP] [PATCH 4/4] libswap: add Btrfs noCOW attribute setting for swap files Li Wang
2024-01-22 8:40 ` Petr Vorel
2024-01-22 8:47 ` Petr Vorel
2024-01-22 9:20 ` Li Wang
2024-01-22 9:04 ` Li Wang
2024-01-22 9:03 ` [LTP] [PATCH 1/4] libswap: add known swap supported fs check Petr Vorel
2024-01-22 9:12 ` Li Wang
2024-01-22 10:57 ` Petr Vorel
2024-01-22 9:41 ` Petr Vorel
2024-01-22 10:22 ` Li Wang
2024-01-22 9:13 ` Petr Vorel
2024-01-22 9:32 ` Li Wang
2024-01-22 11:03 ` Petr Vorel
2024-01-22 14:23 ` Li Wang
2024-01-22 20:23 ` Petr Vorel [this message]
2024-01-23 5:55 ` Li Wang
2024-01-23 7:30 ` Li Wang
2024-01-23 7:48 ` Petr Vorel
2024-01-23 12:04 ` Li Wang
2024-01-23 12:31 ` Petr Vorel
2024-01-23 13:10 ` Li Wang
2024-01-23 15:45 ` Petr Vorel
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=20240122202325.GA119341@pevik \
--to=pvorel@suse.cz \
--cc=liwang@redhat.com \
--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