From: Petr Vorel <pvorel@suse.cz>
To: "Bird, Tim" <Tim.Bird@sony.com>
Cc: Joerg Vehlow <joerg.vehlow@aox-tech.de>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Richard Palethorpe <rpalethorpe@suse.com>,
"ltp@lists.linux.it" <ltp@lists.linux.it>,
"automated-testing@lists.yoctoproject.org"
<automated-testing@lists.yoctoproject.org>
Subject: Re: [LTP] [PATCH 1/6] tst_fs_type: Add nsfs, vfat, squashfs to tst_fs_type_name()
Date: Mon, 29 Aug 2022 18:49:33 +0200 [thread overview]
Message-ID: <YwzuHaRJC+gUPd63@pevik> (raw)
In-Reply-To: <BYAPR13MB250348CBA4E0B0333C5CF54AFD769@BYAPR13MB2503.namprd13.prod.outlook.com>
> > -----Original Message-----
> > From: Petr Vorel <pvorel@suse.cz>
> > Hi Tim,
> > > Minor nit, but the subject line has nsfs when I think it means ntfs.
> > > -- Tim
> > Thanks, will be fixed in v2.
> > How about XFS using 300 MB vs 16 MB but using different code paths?
> > How big deal it'd be if we require 300 MB in case testing on kernel with XFS
> > enabled and xfsprogs installed?
> > https://lore.kernel.org/ltp/YwyYUzvlxfIGpTwo@yuki/
> > https://lore.kernel.org/ltp/YwyljsgYIK3AvUr+@pevik/
> I'm not personally aware of any uses of XFS in embedded projects, let alone
> ones with a filesystem size of less than 300 MB. So I think it would be OK.
> Such a test might hit some lightly used codepaths, so it might have more likelihood
> to reveal a bug in XFS. But if literally no one is using XFS in this configuration,
> I'm not sure how valuable the testing would be.
> That said, my knowledge of the embedded ecosystem is not comprehensive.
> I just posted a question about this on the celinux-dev and Linux-embedded
> mailing lists. I let you know if I hear of anyone using an XFS filesystem less
> than 300 MB in size in their embedded Linux project or device.
> -- Tim
Thanks a lot, Tim!
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-08-29 16:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 0:28 [LTP] [PATCH 0/6] Track minimal size per filesystem Petr Vorel
2022-08-27 0:28 ` [LTP] [PATCH 1/6] tst_fs_type: Add nsfs, vfat, squashfs to tst_fs_type_name() Petr Vorel
2022-08-29 10:44 ` Cyril Hrubis
2022-08-29 15:46 ` Bird, Tim
2022-08-29 16:14 ` Petr Vorel
2022-08-29 16:35 ` Bird, Tim
2022-08-29 16:49 ` Petr Vorel [this message]
2022-08-30 5:59 ` Li Wang
2022-08-27 0:28 ` [LTP] [PATCH 2/6] API: tst_device: Track minimal size per filesystem Petr Vorel
2022-08-29 10:58 ` Cyril Hrubis
2022-08-29 11:29 ` Petr Vorel
2022-08-29 12:24 ` [LTP] [Automated-testing] " Cyril Hrubis
2022-08-30 6:11 ` [LTP] " Li Wang
2022-08-27 0:28 ` [LTP] [PATCH 3/6] tst_test: Use 16 MB also for tmpfs Petr Vorel
2022-08-29 11:00 ` Cyril Hrubis
2022-08-30 6:12 ` Li Wang
2022-08-27 0:28 ` [LTP] [PATCH 4/6] tst_device: Use getopts Petr Vorel
2022-08-29 11:03 ` [LTP] [Automated-testing] " Cyril Hrubis
2022-08-29 11:42 ` Petr Vorel
2022-08-30 6:14 ` [LTP] " Li Wang
2022-08-27 0:28 ` [LTP] [PATCH 5/6] tst_device: Add support -f filesystem Petr Vorel
2022-08-29 11:04 ` Cyril Hrubis
2022-08-30 6:14 ` Li Wang
2022-08-27 0:28 ` [LTP] [PATCH 6/6] tst_test.sh: Pass used filesystem to tst_device Petr Vorel
2022-08-29 11:05 ` Cyril Hrubis
2022-08-30 6:16 ` Li Wang
2022-08-29 10:43 ` [LTP] [Automated-testing] [PATCH 0/6] Track minimal size per filesystem Cyril Hrubis
2022-08-29 11:39 ` Petr Vorel
2022-08-30 5:52 ` Li Wang
2022-08-30 8:18 ` 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=YwzuHaRJC+gUPd63@pevik \
--to=pvorel@suse.cz \
--cc=Tim.Bird@sony.com \
--cc=automated-testing@lists.yoctoproject.org \
--cc=joerg.vehlow@aox-tech.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.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 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).