From: Petr Vorel <pvorel@suse.cz>
To: SANDUR Suresh <suresh-s.sandur@thalesgroup.com>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] Need info on LTP tests that use /dev/loop mount device.
Date: Wed, 23 Nov 2022 13:00:54 +0100 [thread overview]
Message-ID: <Y34Ldi2CIHPYc8Hk@pevik> (raw)
In-Reply-To: <MR1P264MB3953913324A116A1E9CADE40A80D9@MR1P264MB3953.FRAP264.PROD.OUTLOOK.COM>
Hi Suresh,
> Hello,
> I am trying to understand the test cases that use the /dev/loop* device. For example the following tests use the loop device:
> chmod06, chown04, chown04_16, create06, fallocate04, fallocate05 and fsetxattr01
> What is the purpose of using the /dev/loop device? Is it to test some feature of the FS which cannot be done with the currently mounted FS? For example, execute the testcase on a RO filesystem? Are there any others? I am not sure about this, but does LTP also do something like mount the loop device and put different FS, like ext2, ext3, ext4, xfs on the loop device and run the same testcase?
/dev/loop is used for .all_filesystems to run the test on various filesystems
(btrfs, exfat, ext2, ext3, fuse, ntfs, vfat, tmpfs, xfs). But you could pass a
real device via environment variable $LTP_DEV.
https://github.com/linux-test-project/ltp/wiki/C-Test-API#115-testing-with-a-block-device
https://github.com/linux-test-project/ltp/wiki/C-Test-API#113-filesystem-type-detection-and-skiplist
Kind regards,
Petr
> regards,
> Suresh
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-11-23 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 15:56 [LTP] Need info on LTP tests that use /dev/loop mount device SANDUR Suresh via ltp
2022-11-23 12:00 ` Petr Vorel [this message]
[not found] ` <MR1P264MB395376B3E3DAAA7E33BE24B5A80C9@MR1P264MB3953.FRAP264.PROD.OUTLOOK.COM>
[not found] ` <MR1P264MB3233CF6C132C977798EB16819F0C9@MR1P264MB3233.FRAP264.PROD.OUTLOOK.COM>
2022-11-25 14:00 ` SANDUR Suresh via ltp
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=Y34Ldi2CIHPYc8Hk@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=suresh-s.sandur@thalesgroup.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.