From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: log recovery needs to be aware of CONFIG_XFS_RT now
Date: Mon, 8 Feb 2016 20:06:08 -0600 [thread overview]
Message-ID: <56B94990.5080707@sandeen.net> (raw)
In-Reply-To: <20160208233350.GO27429@dastard>
On 2/8/16 5:33 PM, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> As it uses buffer verifiers that only exist when CONFIG_XFS_RT=y.
>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
> ---
> Note: I will fold this back into the original patch that caused
> this build regression and rebuild the for-next tree.
>
> fs/xfs/xfs_log_recover.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fs/xfs/xfs_log_recover.c b/fs/xfs/xfs_log_recover.c
> index 23ad143..1dc0e14 100644
> --- a/fs/xfs/xfs_log_recover.c
> +++ b/fs/xfs/xfs_log_recover.c
> @@ -2472,11 +2472,13 @@ xlog_recover_validate_buf_type(
> }
> bp->b_ops = &xfs_sb_buf_ops;
> break;
> +#ifdef CONFIG_XFS_RT
> case XFS_BLFT_RTBITMAP_BUF:
> case XFS_BLFT_RTSUMMARY_BUF:
> /* no magic numbers for verification of RT buffers */
> bp->b_ops = &xfs_rtbuf_ops;
> break;
> +#endif /* CONFIG_XFS_RT */
> default:
> xfs_warn(mp, "Unknown buffer type %d!",
> xfs_blft_from_flags(buf_f));
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2016-02-09 2:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 6:07 [ANNOUNCE] xfs: for-next branch updated to 4a91310 Dave Chinner
2016-02-08 15:37 ` Brian Foster
2016-02-08 19:52 ` Dave Chinner
2016-02-08 23:33 ` [PATCH] xfs: log recovery needs to be aware of CONFIG_XFS_RT now Dave Chinner
2016-02-09 2:06 ` Eric Sandeen [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=56B94990.5080707@sandeen.net \
--to=sandeen@sandeen.net \
--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