From: Eric Sandeen <sandeen@redhat.com>
To: "'linux-xfs@oss.sgi.com'" <linux-xfs@oss.sgi.com>
Subject: [PATCH, RFC] xfs: don't verify checksum on non-V5 superblocks
Date: Thu, 15 Aug 2013 13:19:15 -0500 [thread overview]
Message-ID: <520D1BA3.1050500@redhat.com> (raw)
The current test in xfs_sb_read_verify() will attempt to validate
an sb checksum if sb_crc is non-zero, even if the superblock is not
marked as being version 5.
This runs the risk of picking up random garbage in sb_crc for non-V5
superblocks; such garbage is known to exist in the wild due to prior bugs.
This will cause verification to fail for otherwise non-fatal reasons.
I'm not sure of the point of trying to validate a non-V5 superblock;
is there one? Shouldn't this || be an &&? (Can sb_crc validly be
0 for a V5 SB?)
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
diff --git a/fs/xfs/xfs_mount.c b/fs/xfs/xfs_mount.c
index 2b0ba35..5ca299b 100644
--- a/fs/xfs/xfs_mount.c
+++ b/fs/xfs/xfs_mount.c
@@ -764,7 +764,7 @@ xfs_sb_read_verify(
*/
if (dsb->sb_magicnum == cpu_to_be32(XFS_SB_MAGIC) &&
(((be16_to_cpu(dsb->sb_versionnum) & XFS_SB_VERSION_NUMBITS) ==
- XFS_SB_VERSION_5) ||
+ XFS_SB_VERSION_5) &&
dsb->sb_crc != 0)) {
if (!xfs_verify_cksum(bp->b_addr, be16_to_cpu(dsb->sb_sectsize),
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-08-15 18:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 18:19 Eric Sandeen [this message]
2013-08-15 19:45 ` [PATCH, RFC] xfs: don't verify checksum on non-V5 superblocks Ben Myers
2013-08-15 21:00 ` Dave Chinner
2013-08-15 21:15 ` Eric Sandeen
2013-08-15 22:41 ` [PATCH, RFC] xfs: be more forgiving of a v4 secondary sb w/ junk in v5 fields Eric Sandeen
2013-08-15 23:15 ` Dave Chinner
2013-09-09 20:33 ` [PATCH V2] " Eric Sandeen
2013-09-09 21:08 ` Mark Tinguely
2013-09-09 21:10 ` Eric Sandeen
2013-09-09 21:16 ` Mark Tinguely
2013-10-31 15:51 ` Ben Myers
2013-10-17 20:17 ` [PATCH, RFC] " Ben Myers
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=520D1BA3.1050500@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.