From: Brian Foster <bfoster@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 3/4] xfs: validate sb_logsunit is a multiple of the fs blocksize
Date: Thu, 26 Oct 2017 09:16:49 -0400 [thread overview]
Message-ID: <20171026131648.GC3450@bfoster.bfoster> (raw)
In-Reply-To: <150899697674.18095.8949507524525909891.stgit@magnolia>
On Wed, Oct 25, 2017 at 10:49:36PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> Make sure the log stripe unit is sane before proceeding with mounting.
> AFAICT this means that logsunit has to be 0, 1, or a multiple of the fs
> block size. Found this by setting the LSB of logsunit in xfs/350 and
> watching the system crash as soon as we try to write to the log.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
Reviewed-by: Brian Foster <bfoster@redhat.com>
> fs/xfs/xfs_log.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
>
> diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
> index dc95a49..4edb36f 100644
> --- a/fs/xfs/xfs_log.c
> +++ b/fs/xfs/xfs_log.c
> @@ -608,6 +608,7 @@ xfs_log_mount(
> xfs_daddr_t blk_offset,
> int num_bblks)
> {
> + bool fatal = xfs_sb_version_hascrc(&mp->m_sb);
> int error = 0;
> int min_logfsbs;
>
> @@ -659,9 +660,20 @@ xfs_log_mount(
> XFS_FSB_TO_B(mp, mp->m_sb.sb_logblocks),
> XFS_MAX_LOG_BYTES);
> error = -EINVAL;
> + } else if (mp->m_sb.sb_logsunit > 1 &&
> + mp->m_sb.sb_logsunit % mp->m_sb.sb_blocksize) {
> + xfs_warn(mp,
> + "log stripe unit %u bytes must be a multiple of block size",
> + mp->m_sb.sb_logsunit);
> + error = -EINVAL;
> + fatal = true;
> }
> if (error) {
> - if (xfs_sb_version_hascrc(&mp->m_sb)) {
> + /*
> + * Log check errors are always fatal on v5; or whenever bad
> + * metadata leads to a crash.
> + */
> + if (fatal) {
> xfs_crit(mp, "AAIEEE! Log failed size checks. Abort!");
> ASSERT(0);
> goto out_free_log;
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-10-26 13:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 5:49 [PATCH 1/4] xfs: refactor extended attribute list operation Darrick J. Wong
2017-10-26 5:49 ` [PATCH 2/4] xfs: abort dir/attr btree operation if btree is obviously weird Darrick J. Wong
2017-10-26 13:16 ` Brian Foster
2017-10-26 16:54 ` Darrick J. Wong
2017-10-26 5:49 ` [PATCH 3/4] xfs: validate sb_logsunit is a multiple of the fs blocksize Darrick J. Wong
2017-10-26 13:16 ` Brian Foster [this message]
2017-10-26 5:49 ` [PATCH 4/4] xfs: compare btree block keys to parent block's keys during scrub Darrick J. Wong
2017-10-26 13:16 ` Brian Foster
2017-10-26 16:55 ` Darrick J. Wong
2017-10-26 13:16 ` [PATCH 1/4] xfs: refactor extended attribute list operation Brian Foster
2017-10-26 16:45 ` Darrick J. Wong
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=20171026131648.GC3450@bfoster.bfoster \
--to=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--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