From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Cc: bpm@sgi.com
Subject: [PATCH 0/6] xfs: fixes for 3.10-rc4
Date: Mon, 3 Jun 2013 15:28:45 +1000 [thread overview]
Message-ID: <1370237332-24757-1-git-send-email-david@fromorbit.com> (raw)
Hi Ben,
He's an up-to-date set of patches remaining for 3.10. It fixes the
dquot crc calc that Brain pointed out, as well are removes the
unnecessary xfs_iunlink_dinode_calc_crc() function.
There's also a new patch that deals with rejecting the noattr2 mount
option for CRC enabled filesystems. attr2 is always enabled for
them, so the noattr2 mount option needs to be rejected as invalid.
Cheers,
Dave.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-06-03 5:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 5:28 Dave Chinner [this message]
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
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=1370237332-24757-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.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