From: Eryu Guan <eguan@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] generic: reserve correct indirect blocks for delalloc write path
Date: Mon, 4 Sep 2017 23:44:04 +0800 [thread overview]
Message-ID: <20170904154404.GB27835@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170904151440.GE4671@magnolia>
On Mon, Sep 04, 2017 at 08:14:40AM -0700, Darrick J. Wong wrote:
> On Mon, Sep 04, 2017 at 05:38:19PM +0800, Eryu Guan wrote:
> > Test that XFS reserves reasonable indirect blocks for delalloc and
> > speculative allocation, and doesn't cause any fdblocks corruption.
> >
> > This was inspired by an XFS but that too large 'indlen' was returned by
> > xfs_bmap_worst_indlen() which can't fit in a 17 bits value
> > (STARTBLOCKVALBITS is defined as 17), then leaked 1 << 17 blocks in
> > sb_fdblocks.
> >
> > This was only seen on XFS with rmapbt feature enabled, but nothing
> > prevents the test from being a generic test.
> >
> > Signed-off-by: Eryu Guan <eguan@redhat.com>
> > ---
> >
> > This reproduces sb_fdblocks corruption issue for me with 1k block size
> > rmapbt enabled XFS on x86_64 and ppc64 hosts. Other block size XFS pass
> > the test now.
>
> Looks reasonable; does the revert patch (posted earlier) fix it?
Yes, I just confirmed that the revert patch did fix the bug for me.
Thanks,
Eryu
prev parent reply other threads:[~2017-09-04 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 9:38 [PATCH] generic: reserve correct indirect blocks for delalloc write path Eryu Guan
2017-09-04 15:14 ` Darrick J. Wong
2017-09-04 15:44 ` Eryu Guan [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=20170904154404.GB27835@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@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