public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Brian Foster <bfoster@redhat.com>
Cc: bpm@sgi.com, xfs@oss.sgi.com
Subject: Re: [PATCH 3/6] xfs: inode unlinked list needs to recalculate the inode CRC
Date: Tue, 4 Jun 2013 13:06:20 +1000	[thread overview]
Message-ID: <20130604030620.GC29466@dastard> (raw)
In-Reply-To: <51ACDE03.4090501@redhat.com>

On Mon, Jun 03, 2013 at 02:18:43PM -0400, Brian Foster wrote:
> On 06/03/2013 01:28 AM, Dave Chinner wrote:
> > From: Dave Chinner <dchinner@redhat.com>
> > 
> > The inode unlinked list manipulations operate directly on the inode
> > buffer, and so bypass the inode CRC calculation mechanisms. Hence an
> > inode on the unlinked list has an invalid CRC. Fix this by
> > recalculating the CRC whenever we modify an unlinked list pointer in
> > an inode, ncluding during log recovery. This is trivial to do and
> > results in  unlinked list operations always leaving a consistent
> > inode in the buffer.
> > 
> > Signed-off-by: Dave Chinner <dchinner@redhat.com>
.....
> > @@ -1809,6 +1821,10 @@ xfs_iunlink_remove(
> >  		last_dip->di_next_unlinked = cpu_to_be32(next_agino);
> >  		ASSERT(next_agino != 0);
> >  		offset = last_offset + offsetof(xfs_dinode_t, di_next_unlinked);
> > +
> > +		/* need to recalc the inode CRC if appropriate */
> > +		xfs_dinode_calc_crc(mp, dip);
> > +
> 
> Ugh, sorry I didn't notice this last time around, but this one looks
> like it should recalculate the crc on last_dip instead of dip.

Yup, it should - good catch. This just highlights how hard it is to
actaully catch a filesystem in the state with a corrupt CRC on the
unlinked list...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-06-04  3:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03  5:28 [PATCH 0/6] xfs: fixes for 3.10-rc4 Dave Chinner
2013-06-03  5:28 ` [PATCH 1/6] xfs: rework dquot CRCs Dave Chinner
2013-06-03 18:18   ` Brian Foster
2013-06-04 21:46     ` Ben Myers
2013-06-04 22:07       ` Ben Myers
2013-06-03  5:28 ` [PATCH 2/6] xfs: fix log recovery transaction item reordering Dave Chinner
2013-06-03  5:28 ` [PATCH 3/6] xfs: inode unlinked list needs to recalculate the inode CRC Dave Chinner
2013-06-03 18:18   ` Brian Foster
2013-06-04  3:06     ` Dave Chinner [this message]
2013-06-03  5:28 ` [PATCH 4/6] xfs: fix remote attribute invalidation for a leaf Dave Chinner
2013-06-03 18:59   ` Brian Foster
2013-06-03 19:09   ` Mark Tinguely
2013-06-04  3:13     ` Dave Chinner
2013-06-04 22:28   ` Ben Myers
2013-06-03  5:28 ` [PATCH 5/6] xfs: disable noattr2/attr2 mount options for CRC enabled filesystems Dave Chinner
2013-06-03 19:02   ` Brian Foster
2013-06-03 21:38   ` Mark Tinguely
2013-06-05  1:49     ` Dave Chinner
2013-06-03  5:28 ` [PATCH 6/6] xfs: increase number of ACL entries for V5 superblocks Dave Chinner
2013-06-03 22:08   ` Mark Tinguely
2013-06-04  3:26     ` Dave Chinner
2013-06-05  1:58       ` Dave Chinner
2013-06-04 15:34   ` Ben Myers
2013-06-04 22:29     ` Dave Chinner
2013-06-04 22:32       ` 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=20130604030620.GC29466@dastard \
    --to=david@fromorbit.com \
    --cc=bfoster@redhat.com \
    --cc=bpm@sgi.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