From: Cyril Hrubis <chrubis@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] Fix ioctl_ficlone on XFS without reflink support
Date: Tue, 1 Oct 2024 13:39:52 +0200 [thread overview]
Message-ID: <ZvvfiHR0Fr76SbuO@yuki.lan> (raw)
In-Reply-To: <cc358271-b656-4314-9cc7-83429b24aba2@suse.cz>
Hi!
> > I suppose that we need to add .mkfs_ver string to the struct tst_fs and
> > possibly .kernel_ver as well so that we can add both checks to the
> > structures as:
> >
> > {
> > .type = "xfs",
> > .mkfs_ver = ">= 5.1.0",
> > .kernel_ver = ">= 4.9.0",
> > ...
> > }
>
> It'd be simpler to add .skip_if_unsupported flag to struct tst_fs and
> then simply TCONF the single filesystem if mount() returns EOPNOTSUPP.
> That way we don't need hardcoded version checks for the kernel. MKFS
> versions checks would still be needed, though.
That's not a 100% correct either, with that we will not catch if the
functionality was disabled in the kernel by a mistake.
So I think that we need:
- minimal kernel version where the functionality was added in upstream
in the tst_fs structure
- try to mount the fs
- if we get EOPNOTSUPP and current kernel is older than the minimal
version report TCONF
- otherwise report TFAIL
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2024-10-01 11:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 12:53 [LTP] [PATCH] Fix ioctl_ficlone on XFS without reflink support Andrea Cervesato
2024-09-26 11:57 ` Cyril Hrubis
2024-09-26 14:58 ` Andrea Cervesato via ltp
2024-09-26 15:40 ` Cyril Hrubis
2024-09-27 7:44 ` Andrea Cervesato via ltp
2024-09-27 7:49 ` Cyril Hrubis
2024-09-27 14:41 ` Martin Doucha
2024-09-30 8:48 ` Cyril Hrubis
2024-09-30 8:53 ` Cyril Hrubis
2024-10-01 11:39 ` Cyril Hrubis [this message]
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=ZvvfiHR0Fr76SbuO@yuki.lan \
--to=chrubis@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox