From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-xfs <linux-xfs@vger.kernel.org>,
Dave Chinner <david@fromorbit.com>
Subject: Re: [PATCH] mkfs: don't use xfs_verify_fsbno() before m_sb is fully set up
Date: Tue, 9 Jul 2019 23:09:52 -0700 [thread overview]
Message-ID: <20190710060952.GU1404256@magnolia> (raw)
In-Reply-To: <d04c688e-4d67-83f4-8401-d064d13bdc33@redhat.com>
On Tue, Jul 09, 2019 at 03:09:00PM -0500, Eric Sandeen wrote:
> Commit 8da5298 mkfs: validate start and end of aligned logs stopped
> open-coding log end block checks, and used xfs_verify_fsbno() instead.
> It also used xfs_verify_fsbno() to validate the log start. This
> seemed to make sense, but then xfs/306 started failing on 4k sector
> filesystems, which leads to a log striep unite being set on a single
> AG filesystem.
>
> As it turns out, if xfs_verify_fsbno() is testing a block in the
> last AG, it needs to have mp->m_sb.sb_dblocks set, which isn't done
> until later. With sb_dblocks unset we can't know how many blocks
> are in the last AG, and hence can't validate it.
>
> To fix all this, go back to open-coding the checks; note that this
> /does/ rely on m_sb.sb_agblklog being set, but that /is/ already
> done in the early call to start_superblock_setup().
>
> Fixes: 8da5298 ("mkfs: validate start and end of aligned logs")
> Reported-by: Dave Chinner <david@fromorbit.com>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
>
> Sorry for missing this one in regression testing :/
Sorry for totally not noticing that we're validating using an incomplete
xfs_mount... <grumble>
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
>
> diff --git a/mkfs/xfs_mkfs.c b/mkfs/xfs_mkfs.c
> index 468b8fde..4e576a5c 100644
> --- a/mkfs/xfs_mkfs.c
> +++ b/mkfs/xfs_mkfs.c
> @@ -3040,7 +3040,7 @@ align_internal_log(
> cfg->logstart = ((cfg->logstart + (sunit - 1)) / sunit) * sunit;
>
> /* If our log start overlaps the next AG's metadata, fail. */
> - if (!xfs_verify_fsbno(mp, cfg->logstart)) {
> + if (XFS_FSB_TO_AGBNO(mp, cfg->logstart) <= XFS_AGFL_BLOCK(mp)) {
> fprintf(stderr,
> _("Due to stripe alignment, the internal log start (%lld) cannot be aligned\n"
> "within an allocation group.\n"),
> @@ -3051,10 +3051,9 @@ _("Due to stripe alignment, the internal log start (%lld) cannot be aligned\n"
> /* round up/down the log size now */
> align_log_size(cfg, sunit);
>
> - /* check the aligned log still fits in an AG. */
> + /* check the aligned log still starts and ends in the same AG. */
> logend = cfg->logstart + cfg->logblocks - 1;
> - if (XFS_FSB_TO_AGNO(mp, cfg->logstart) != XFS_FSB_TO_AGNO(mp, logend) ||
> - !xfs_verify_fsbno(mp, logend)) {
> + if (XFS_FSB_TO_AGNO(mp, cfg->logstart) != XFS_FSB_TO_AGNO(mp, logend)) {
> fprintf(stderr,
> _("Due to stripe alignment, the internal log size (%lld) is too large.\n"
> "Must fit within an allocation group.\n"),
>
prev parent reply other threads:[~2019-07-10 6:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 20:09 [PATCH] mkfs: don't use xfs_verify_fsbno() before m_sb is fully set up Eric Sandeen
2019-07-09 20:33 ` Eric Sandeen
2019-07-10 6:09 ` Darrick J. Wong [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=20190710060952.GU1404256@magnolia \
--to=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@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