From: Anthony Iliopoulos <ailiopoulos@suse.com>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] xfs/513: fix allocsize on archs with pagesize larger than blocksize
Date: Sat, 7 Mar 2020 11:51:41 +0100 [thread overview]
Message-ID: <20200307105141.GM11781@technoir> (raw)
In-Reply-To: <20200307071512.GB14282@dhcp-12-102.nay.redhat.com>
On Sat, Mar 07, 2020 at 03:15:12PM +0800, Zorro Lang wrote:
> On Sat, Mar 07, 2020 at 01:44:07AM +0100, Anthony Iliopoulos wrote:
> > The minimum accepted allocsize mount option value is page size, which
> > causes the particular test to fail in architectures where page size >
> > block size. Fix it by basing the value on the platform page size rather
> > than the block size as obtained from mkfs. In addition add a filter so
> > that different values can be used without breaking the golden output.
> >
> > Signed-off-by: Anthony Iliopoulos <ailiopoulos@suse.com>
> > ---
>
> Hi,
>
> Thanks for this patch, I've forgotten that I tried to fix it:
> https://marc.info/?l=fstests&m=158250811523489&w=2
>
> And looks like Eryu prefer filtering the PAGESIZE, he might like to merge
> this one:)
I missed that, but assumed that the intention of the test was to cover
the minimum allowable value on the allocsize range and not just the
parsing, so I made it variable. Either way it's fine as long as the test
covers the intended purpose.
> The patch looks good to me, only one slight thing. The filter_pagesz() is
> not used to filter "$pagesize" itself, it filters "allocsize=$pagesize"
> actually. So how about name it as filter_xfs_options (or something like that),
> then we might add more lines(filter) in it later?
Thanks for the review, yes this makes sense, so I'll send a v2 shortly
with the changes.
prev parent reply other threads:[~2020-03-07 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 0:44 [PATCH] xfs/513: fix allocsize on archs with pagesize larger than blocksize Anthony Iliopoulos
2020-03-07 7:15 ` Zorro Lang
2020-03-07 10:51 ` Anthony Iliopoulos [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=20200307105141.GM11781@technoir \
--to=ailiopoulos@suse.com \
--cc=fstests@vger.kernel.org \
--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