linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeffle Xu <jefflexu@linux.alibaba.com>
To: fstests@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, joseph.qi@linux.alibaba.com,
	Jeffle Xu <jefflexu@linux.alibaba.com>
Subject: [PATCH RFC 0/2] fsx: make fsx perceptive to cluster size
Date: Fri, 24 Apr 2020 17:33:48 +0800	[thread overview]
Message-ID: <1587720830-11955-1-git-send-email-jefflexu@linux.alibaba.com> (raw)

Offset and size should be aligned with cluster_size when inserting or
collapsing range on ext4 with 'bigalloc' enabled. Currently fsx only
align offset/size with block size.

In fact I have no idea which is the best way to fix this isue. On one hand,
fsx should be general and has no knowledge of the underlying filesystem.
Besides the cluster size seems to be stored on ext4_super_block and there's
no easy way to get it. But on the oter hand, quite many tests call fsx
directly, e.g., generic/127, rather than the generic routine run_fsx()
defined in common/rc.


Jeffle Xu (2):
  xfstests: fsx: add support for cluster size
  xfstests: common/rc: add cluster size support for ext4

 common/rc |  9 +++++++++
 ltp/fsx.c | 20 ++++++++++++++------
 2 files changed, 23 insertions(+), 6 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2020-04-24  9:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24  9:33 Jeffle Xu [this message]
2020-04-24  9:33 ` [PATCH RFC 1/2] xfstests: fsx: add support for cluster size Jeffle Xu
2020-04-27 17:29   ` Darrick J. Wong
2020-04-29  7:22     ` JeffleXu
2020-04-24  9:33 ` [PATCH RFC 2/2] xfstests: common/rc: add cluster size support for ext4 Jeffle Xu
2020-04-27 17:33   ` Darrick J. Wong

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=1587720830-11955-1-git-send-email-jefflexu@linux.alibaba.com \
    --to=jefflexu@linux.alibaba.com \
    --cc=fstests@vger.kernel.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-ext4@vger.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;
as well as URLs for NNTP newsgroup(s).