public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/3]xfs: growfs infrastructure changes for 3.8
Date: Thu,  8 Nov 2012 16:39:30 +1100	[thread overview]
Message-ID: <1352353173-18820-1-git-send-email-david@fromorbit.com> (raw)

Hi folks.

The following 3 patches are changes to growfs necessary for supporting CRC
verification of metadata. The first converts AG btree root blocks to use the
generic btree header block initialisation code so CRC support only needs to be
added in one place. The second allows verifiers to distinguish between a write
for growfs whenteh xfs-perag is not fully initialised by using uncached buffers.
And the last adds initialisation of the AGFL during growfs, which we currently
don't do at all.

These are also patches for the 3.8 cycle i'd lik eto see in the 3.8 cycle - the
more infrastructure changes that get done in 3.8, the less there will be when
the format changes and CRCs patches arrive for the 3.9 cycle...

Cheers,

Dave.

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

             reply	other threads:[~2012-11-08  5:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-08  5:39 Dave Chinner [this message]
2012-11-08  5:39 ` [PATCH 1/3] xfs: use btree block initialisation functions in growfs Dave Chinner
2012-11-08  5:39 ` [PATCH 2/3] xfs: growfs: use uncached buffers for new headers Dave Chinner
2012-11-08  5:39 ` [PATCH 3/3] xfs: make growfs initialise the AGFL header Dave Chinner

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=1352353173-18820-1-git-send-email-david@fromorbit.com \
    --to=david@fromorbit.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