public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@kernel.org>
To: ltp@lists.linux.it
Cc: linux-btrfs@vger.kernel.org, zlang@redhat.com
Subject: [PATCH 0/3] LTP random fixes for xfs and btrfs
Date: Sun,  1 Dec 2024 17:36:03 +0800	[thread overview]
Message-ID: <20241201093606.68993-1-zlang@kernel.org> (raw)

[PATCH 1/3] ioctl_ficlone02.c: set all_filesystems to zero

  It doesn't skip filesystems as its plan, fix it.

[PATCH 2/3] stat04+lstat03: fix bad blocksize mkfs option for xfs

  mkfs.xfs doesn't support "-b 1024", needs "-b size=1024"

[PATCH 3/3] stat04+lstat03: skip test on btrfs

  The "-b" option of mkfs.btrfs isn't a blocksize option, there's not blocksize
  option in mkfs.btrfs. So I'd like to skip this test for btrfs. But I'm not
  sure if there's better way, so CC *btrfs list* to get more review points for
  that.
  (BTW, better to have a common helper to deal with different filesystems'
   blocksize options in the future)

             reply	other threads:[~2024-12-01  9:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-01  9:36 Zorro Lang [this message]
2024-12-01  9:36 ` [PATCH 1/3] ioctl_ficlone02.c: set all_filesystems to zero Zorro Lang
2024-12-02 13:36   ` [LTP] " 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
2024-12-09  6:14           ` Petr Vorel
2024-12-11 12:08             ` Cyril Hrubis
2024-12-11 19:40               ` Petr Vorel
2024-12-01  9:36 ` [PATCH 2/3] stat04+lstat03: fix bad blocksize mkfs option for xfs Zorro Lang
2024-12-02 13:56   ` [LTP] " Cyril Hrubis
2024-12-01  9:36 ` [PATCH 3/3] stat04+lstat03: skip test on btrfs Zorro Lang
2024-12-02 13:55   ` [LTP] " Cyril Hrubis
2024-12-01  9:55 ` [PATCH 0/3] LTP random fixes for xfs and btrfs Qu Wenruo
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=20241201093606.68993-1-zlang@kernel.org \
    --to=zlang@kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=ltp@lists.linux.it \
    --cc=zlang@redhat.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