public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Tinguely <tinguely@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH TARBALL, DEV ONLY] xfsprogs: metadata CRC support V2
Date: Thu, 25 Apr 2013 11:37:37 -0500	[thread overview]
Message-ID: <51795BD1.8020003@sgi.com> (raw)
In-Reply-To: <20130412145555.GF30622@dastard>

On 04/12/13 09:55, Dave Chinner wrote:
> Hi folks,
>
> I've attached a tarball containing the patch series that adds
> metadata CRC support to xfsprogs. It is still very much a work in
> progress, but is sufficient to start running xfstests on CRC enable
> filesystems.
>
> THere is much missing functionality, especially with respect to
> directly/attribute modifications. Only mkfs and xfs_repair have been
> updated to explicitly support CRC on directory/sttribute blocks,
> though all the other tools will stil run the result might be a
> little unpredictable.
>
> The patch series is as follows:
>
> Dave Chinner (26):
>        xfsprogs: sync code to current kernel code
>        xfsprogs: update libxfs to 3.9-rc1 + xfsdev
>        xfsprogs: add CRC32c infrastructure
>        xfsprogs: updata libxlog to current kernel code
>        libxfs: add crc format changes to generic btrees
>        xfsprogs: add crc format chagnes to ag headers
>        libxfs: change quota buffer formats
>        libxfs: add version 3 inode support
>        libxfs: add support for crc headers on remote symlinks
>        xfs: add CRC checks to block format directory blocks
>        xfs: add CRC checking to dir2 free blocks
>        xfs: add CRC checking to dir2 data blocks
>        xfs: add CRC checking to dir2 leaf blocks
>        xfs: shortform directory offsets change for dir3 format
>        xfs: add CRCs to dir2/da node blocks
>        xfs: add CRCs to attr leaf blocks
>        xfs: split remote attribute code out
>        xfs: add CRC protection to remote attributes
>        xfs: add buffer types to directory and attribute buffers
>        xfs: buffer type overruns blf_flags field
>        xfs: add CRC checks to the superblock
>        xfs: implement extended feature masks
>        xfsprogs: introduce CRC support into mkfs.xfs
>        xfsprogs: add crc format support to repair
>        xfsprogs: add crc format support to db
>        xfs_repair: update for dir/attr crc format changes.

The patch "logprint-agi-dump" needs a commit message and Signed-off-by.

The patch "debug" be removed (empty) from series and directory.

Thanks,

--Mark.



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

  reply	other threads:[~2013-04-25 16:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12 14:55 [PATCH TARBALL, DEV ONLY] xfsprogs: metadata CRC support V2 Dave Chinner
2013-04-25 16:37 ` Mark Tinguely [this message]
2013-04-25 21:39   ` Dave Chinner
2013-04-25 21:12 ` Mark Tinguely
2013-04-25 21:40   ` Dave Chinner
2013-04-29 21:33     ` Mark Tinguely
2013-04-29 22:09       ` Dave Chinner
2013-04-30 12:03         ` Dave Chinner
2013-04-26  6:12 ` Christoph Hellwig
2013-04-29  1:46   ` Dave Chinner
2013-05-09 12:42 ` Rich Johnston
2013-05-09 13:22   ` Dave Chinner
2013-05-09 13:37     ` Rich Johnston
2013-05-09 13:41       ` Rich Johnston
2013-05-09 20:24         ` Rich Johnston
2013-05-09 22:35       ` Dave Chinner
2013-05-09 23:00         ` Rich Johnston

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=51795BD1.8020003@sgi.com \
    --to=tinguely@sgi.com \
    --cc=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