From: Carlos Maiolino <cmaiolino@redhat.com>
To: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: growfs: don't read garbage for new secondary superblocks
Date: Mon, 8 Oct 2012 14:11:44 -0300 [thread overview]
Message-ID: <20121008171144.GA8313@andromeda.usersys.redhat.com> (raw)
In-Reply-To: <1349697436-14203-1-git-send-email-david@fromorbit.com>
On Mon, Oct 08, 2012 at 10:57:16PM +1100, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> When updating new secondary superblocks in a growfs operation, the
> sueprblock buffer is read from the newly grown region of the
> underlying device. This is not guaranteed to be zero, so violates
> the underlying assumption that the unused parts of superblocks are
> zero filled. Get a new buffer for these secondary superblocks to
> ensure that the unused regions are zero filled correctly.
>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> ---
> fs/xfs/xfs_fsops.c | 21 +++++++++++++++++++--
> 1 file changed, 19 insertions(+), 2 deletions(-)
>
> diff --git a/fs/xfs/xfs_fsops.c b/fs/xfs/xfs_fsops.c
> index c25b094..4beaede 100644
> --- a/fs/xfs/xfs_fsops.c
> +++ b/fs/xfs/xfs_fsops.c
> @@ -399,9 +399,26 @@ xfs_growfs_data_private(
>
> /* update secondary superblocks. */
> for (agno = 1; agno < nagcount; agno++) {
> - error = xfs_trans_read_buf(mp, NULL, mp->m_ddev_targp,
> + error = 0;
> + /*
> + * new secondary superblocks need to be zeroed, not read from
> + * disk as the contents of the new area we are growing into is
> + * completely unknown.
> + */
> + if (agno < oagcount) {
> + error = xfs_trans_read_buf(mp, NULL, mp->m_ddev_targp,
> XFS_AGB_TO_DADDR(mp, agno, XFS_SB_BLOCK(mp)),
> XFS_FSS_TO_BB(mp, 1), 0, &bp);
> + } else {
> + bp = xfs_trans_get_buf(NULL, mp->m_ddev_targp,
> + XFS_AGB_TO_DADDR(mp, agno, XFS_SB_BLOCK(mp)),
> + XFS_FSS_TO_BB(mp, 1), 0);
> + if (bp)
> + xfs_buf_zero(bp, 0, BBTOB(bp->b_length));
> + else
> + error = ENOMEM;
> + }
> +
> if (error) {
> xfs_warn(mp,
> "error %d reading secondary superblock for ag %d",
> @@ -423,7 +440,7 @@ xfs_growfs_data_private(
> break; /* no point in continuing */
> }
> }
> - return 0;
> + return error;
>
> error0:
> xfs_trans_cancel(tp, XFS_TRANS_ABORT);
> --
> 1.7.10
>
Looks good.
Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
--
--Carlos
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-10-08 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 11:57 [PATCH] xfs: growfs: don't read garbage for new secondary superblocks Dave Chinner
2012-10-08 17:11 ` Carlos Maiolino [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=20121008171144.GA8313@andromeda.usersys.redhat.com \
--to=cmaiolino@redhat.com \
--cc=xfs@oss.sgi.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