From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] tst_supported_fs: Implement checking paths against skiplist
Date: Thu, 22 Sep 2022 13:20:15 +0200 [thread overview]
Message-ID: <YyxE7yEZH+E9UXoE@pevik> (raw)
In-Reply-To: <5541d648-f9ba-16c1-6767-4d8838863a25@suse.cz>
> On 22. 09. 22 12:55, Cyril Hrubis wrote:
> > The real problem is that the line between ext2, ext3 and ext4 is really
> > blurry to an extend where it's hard to say which filesystem are you
> > working with. For example while ext2 kernel driver still exists and is
> > in use on embedded hardware modern distributions use single ext driver
> > to handle all three filesystems. Also I think that it was possible to
> > mount ext3 with ext2 driver at some point which disabled the journaling.
Should I understand this that you don't trust /proc/self/mountinfo output?
(show_mountinfo() in fs/proc_namespace.c in kernel git)?
Petr
> Still, I'd argue that blindly assuming any FS with ext2/3/4 magic number is
> always mounted as ext4 is a better solution than returning a string that
> never matches skiplists.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-09-22 11:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 15:50 [LTP] [PATCH] tst_supported_fs: Implement checking paths against skiplist Martin Doucha
2022-09-22 4:16 ` Li Wang
2022-09-22 8:14 ` Martin Doucha
2022-09-22 8:43 ` Petr Vorel
2022-09-22 9:08 ` Li Wang
2022-09-22 9:56 ` Petr Vorel
2022-09-22 9:02 ` Petr Vorel
2022-09-22 9:24 ` Li Wang
2022-09-22 10:40 ` Petr Vorel
2022-09-22 10:55 ` Cyril Hrubis
2022-09-22 10:57 ` Martin Doucha
2022-09-22 11:20 ` Petr Vorel [this message]
2022-09-22 14:42 ` Cyril Hrubis
2022-09-22 20:22 ` Petr Vorel
2022-09-22 8:56 ` Petr Vorel
2022-09-22 20:26 ` Petr Vorel
2022-09-23 10:00 ` Petr Vorel
2022-09-26 7:48 ` Petr Vorel
2022-09-23 15:17 ` 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=YyxE7yEZH+E9UXoE@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
/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.