From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] ioctl_ficlone03.c: Support test on more filesystems
Date: Fri, 11 Jul 2025 16:15:12 +0200 [thread overview]
Message-ID: <aHEccDO8lJiTzbEs@yuki.lan> (raw)
In-Reply-To: <20250326142259.50981-1-pvorel@suse.cz>
Hi!
> + /* ext[234] and tmpfs does not support immutable destination */
> + if (errno_exp == EPERM &&
> + (fs_type == TST_EXT234_MAGIC || fs_type == TST_TMPFS_MAGIC)) {
Maybe a bit better if (tc->dst_fd == immut_fd && ...)
> + errno_exp = EOPNOTSUPP;
> + }
>
> TST_EXP_FAIL(ioctl(*tc->dst_fd, FICLONE, *tc->src_fd),
> - tc->errno_exp,
> - "%s", tc->msg);
> + errno_exp, "%s", tc->msg);
>
> clone_range->src_fd = *tc->src_fd;
>
> TST_EXP_FAIL(ioctl(*tc->dst_fd, FICLONERANGE, clone_range),
> - tc->errno_exp,
> - "%s", tc->msg);
> + errno_exp, "%s", tc->msg);
> }
>
> static void setup(void)
I find it strange that we manage to set the FS_IMMUTABLE_FL in the setup
with the FS_IOC_SETFLAGS without any error. Maybe it would make sense to
check with ext devs what is going on here.
> @@ -117,6 +123,10 @@ static struct tst_test test = {
> .mkfs_ver = "mkfs.xfs >= 1.5.0",
> .mkfs_opts = (const char *const []) {"-m", "reflink=1", NULL},
> },
> + {.type = "ext2"},
> + {.type = "ext3"},
> + {.type = "ext4"},
> + {.type = "tmpfs"},
> {}
> },
> .bufs = (struct tst_buffers []) {
> --
> 2.49.0
>
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-07-11 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 14:22 [LTP] [PATCH 1/1] ioctl_ficlone03.c: Support test on more filesystems Petr Vorel
2025-07-11 14:15 ` Cyril Hrubis [this message]
2025-07-22 10:23 ` Petr Vorel
2025-07-22 11:41 ` Jan Kara
2025-07-22 13:50 ` 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=aHEccDO8lJiTzbEs@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@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