From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfs: for-next branch updated to a444d72e6090
Date: Thu, 8 Dec 2016 07:25:01 +1100 [thread overview]
Message-ID: <20161207202501.GK4326@dastard> (raw)
Hi folks,
The for-next branch of the xfs kernel repository at
git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git
has just been updated. This update contains a bunch of verification
enhancments to detect field corruptions as metadata is read from
disk, faster CRC calculations, a faster buffer cache indexing
structure and some cleanups.
With the merge window likely to open next week, this may be the last
update for the 4.10-rc1 cycle. Let me know if there's anything
critical that I've missed for 4.10 so I can sort it out before the
end of the week.
-Dave.
The new head of the for-next branch is commit:
a444d72e6090 Merge branch 'xfs-4.10-misc-fixes-3' into for-next
New Commits:
Darrick J. Wong (7):
[d2a047f31e86] xfs: forbid AG btrees with level == 0
[bb3be7e7c1c1] xfs: check for bogus values in btree block headers
[356a3225222e] xfs: complain if we don't get nextents bmap records
[96a3aefb8ffd] xfs: don't crash if reading a directory results in an unexpected hole
[0f352f8ee841] xfs: error out if trying to add attrs and anextents > 0
[ef388e2054fe] xfs: don't allow di_size with high bit set
[1bb33a98702d] xfs: don't cap maximum dedupe request length
Dave Chinner (3):
[11ef38afe98c] xfs: make xfs btree stats less huge
[cae028df5344] xfs: optimise CRC updates
[a444d72e6090] Merge branch 'xfs-4.10-misc-fixes-3' into for-next
Eric Sandeen (5):
[6b10b23ca944] xfs: set AGI buffer type in xlog_recover_clear_agi_bucket
[200237d6746f] xfs: Move AGI buffer type setting to xfs_read_agi
[7710517fc37b] xfs: pass state not whichfork to trace_xfs_extlist
[c44a1f22626c] xfs: handle cow fork in xfs_bmap_trace_exlist
[f7a136aee3c1] xfs: several xattr functions can be void
Lucas Stach (1):
[6031e73a5b3f] xfs: use rhashtable to track buffer cache
Code Diffstat:
fs/xfs/libxfs/xfs_alloc.c | 10 +-
fs/xfs/libxfs/xfs_alloc_btree.c | 4 +
fs/xfs/libxfs/xfs_attr_leaf.h | 2 +-
fs/xfs/libxfs/xfs_bmap.c | 14 ++-
fs/xfs/libxfs/xfs_bmap_btree.c | 1 +
fs/xfs/libxfs/xfs_btree.c | 20 ++++
fs/xfs/libxfs/xfs_btree.h | 43 +-------
fs/xfs/libxfs/xfs_cksum.h | 26 ++++-
fs/xfs/libxfs/xfs_dir2_data.c | 2 +-
fs/xfs/libxfs/xfs_ialloc.c | 13 ++-
fs/xfs/libxfs/xfs_ialloc_btree.c | 2 +
fs/xfs/libxfs/xfs_inode_buf.c | 10 +-
fs/xfs/libxfs/xfs_refcount_btree.c | 1 +
fs/xfs/libxfs/xfs_rmap_btree.c | 1 +
fs/xfs/xfs_attr.h | 4 +-
fs/xfs/xfs_attr_list.c | 59 ++++-------
fs/xfs/xfs_buf.c | 120 +++++++++++++---------
fs/xfs/xfs_buf.h | 2 +-
fs/xfs/xfs_file.c | 9 --
fs/xfs/xfs_inode.c | 2 -
fs/xfs/xfs_linux.h | 1 +
fs/xfs/xfs_log.c | 2 +-
fs/xfs/xfs_log_recover.c | 12 ++-
fs/xfs/xfs_mount.c | 7 +-
fs/xfs/xfs_mount.h | 7 +-
fs/xfs/xfs_stats.c | 10 +-
fs/xfs/xfs_stats.h | 200 +++++++++++++++----------------------
fs/xfs/xfs_xattr.c | 23 ++---
28 files changed, 306 insertions(+), 301 deletions(-)
--
Dave Chinner
david@fromorbit.com
next reply other threads:[~2016-12-07 20:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 20:25 Dave Chinner [this message]
2016-12-08 3:32 ` [ANNOUNCE] xfs: for-next branch updated to a444d72e6090 Eryu Guan
2016-12-08 22:57 ` Dave Chinner
2016-12-08 6:36 ` Darrick J. Wong
2016-12-08 22:58 ` 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=20161207202501.GK4326@dastard \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
/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