public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Zorro Lang <zlang@kernel.org>
Cc: linux-btrfs@vger.kernel.org, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 3/3] stat04+lstat03: skip test on btrfs
Date: Mon, 2 Dec 2024 14:55:19 +0100	[thread overview]
Message-ID: <Z028RzZZQjF3pA4Q@yuki.lan> (raw)
In-Reply-To: <20241201093606.68993-4-zlang@kernel.org>

Hi!
> The "-b" option for mkfs.btrfs isn't a blocksize option, it does
> "specify the size of each device as seen by the filesystem" for
> btrfs. There's not an blocksize mkfs option for btrfs, so skip this
> test.
> 
> Signed-off-by: Zorro Lang <zlang@kernel.org>
> ---
>  testcases/kernel/syscalls/lstat/lstat03.c | 2 ++
>  testcases/kernel/syscalls/stat/stat04.c   | 2 ++
>  2 files changed, 4 insertions(+)
> 
> diff --git a/testcases/kernel/syscalls/lstat/lstat03.c b/testcases/kernel/syscalls/lstat/lstat03.c
> index 675fb56f4..f7346893d 100644
> --- a/testcases/kernel/syscalls/lstat/lstat03.c
> +++ b/testcases/kernel/syscalls/lstat/lstat03.c
> @@ -57,6 +57,8 @@ static void setup(void)
>  
>  	if (strcmp(tst_device->fs_type, "xfs") == 0)
>  		snprintf(opt_bsize, sizeof(opt_bsize), "size=%i", pagesize);
> +	else if (strcmp(tst_device->fs_type, "btrfs") == 0)
> +		tst_brk(TCONF, "btrfs is not supported");

This is overkill, all we need to skip on Btrfs is the st_blksize test.
We need to set a flag in the test setup and then skip the corresponding
TST_EXP_EXPR().

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2024-12-02 13:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-01  9:36 [LTP] [PATCH 0/3] LTP random fixes for xfs and btrfs Zorro Lang via ltp
2024-12-01  9:36 ` [LTP] [PATCH 1/3] ioctl_ficlone02.c: set all_filesystems to zero Zorro Lang via ltp
2024-12-02 13:36   ` Cyril Hrubis
2024-12-02 13:59     ` Cyril Hrubis
2024-12-02 14:42       ` Petr Vorel
2024-12-02 15:23         ` Cyril Hrubis
2024-12-03  4:53           ` Petr Vorel
2024-12-03  7:58             ` Cyril Hrubis
2024-12-03  9:24               ` Petr Vorel
2024-12-09  5:53         ` Zorro Lang via ltp
2024-12-09  6:14           ` Petr Vorel
2024-12-09  9:49             ` Zorro Lang via ltp
2024-12-09 10:42               ` Petr Vorel
2024-12-09 11:34               ` Petr Vorel
2024-12-11 12:08             ` Cyril Hrubis
2024-12-11 19:40               ` Petr Vorel
2024-12-01  9:36 ` [LTP] [PATCH 2/3] stat04+lstat03: fix bad blocksize mkfs option for xfs Zorro Lang via ltp
2024-12-02 13:56   ` Cyril Hrubis
2024-12-01  9:36 ` [LTP] [PATCH 3/3] stat04+lstat03: skip test on btrfs Zorro Lang via ltp
2024-12-02 13:55   ` Cyril Hrubis [this message]
2024-12-01  9:55 ` [LTP] [PATCH 0/3] LTP random fixes for xfs and btrfs Qu Wenruo via ltp
2024-12-03 16:22   ` David Sterba

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=Z028RzZZQjF3pA4Q@yuki.lan \
    --to=chrubis@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=ltp@lists.linux.it \
    --cc=zlang@kernel.org \
    /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