From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [ANNOUNCE] xfs: for-next branch updated
Date: Fri, 20 May 2016 11:53:30 +1000 [thread overview]
Message-ID: <20160520015330.GD26977@dastard> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3125 bytes --]
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 is pretty much everything that I will
ask Linus to pull next week after a couple of days in linux-next.
If I've missed anythign critical, let me know.
-Dave.
The new head of the for-next branch is commit:
555b67e Merge branch 'xfs-4.7-inode-reclaim' into for-next
New Commits:
Alex Lyakas (1):
[32b43ab] xfs: optimise xfs_iext_destroy
Brian Foster (1):
[9bdd9bd] xfs: buffer ->bi_end_io function requires irq-safe lock
Carlos Maiolino (7):
[192852b] xfs: configurable error behavior via sysfs
[ffd40ef] xfs: introduce metadata IO error class
[df30939] xfs: add configurable error support to metadata buffers
[ef6a50f] xfs: introduce table-based init for error behaviors
[a5ea70d] xfs: add configuration of error failure speed
[e0a431b3] xfs: add configuration handlers for specific errors
[e6b3bb7] xfs: add "fail at unmount" error handling configuration
Christoph Hellwig (1):
[690a787] xfs: fix warning in xfs_finish_page_writeback for non-debug builds
Dave Chinner (17):
[8179c03] xfs: remove xfs_fs_evict_inode()
[b1438f4] xfs: xfs_iflush_cluster fails to abort on error
[51b07f3] xfs: fix inode validity check in xfs_iflush_cluster
[7d3aa7f] xfs: skip stale inodes in xfs_iflush_cluster
[1f2dcfe] xfs: xfs_inode_free() isn't RCU safe
[8a17d7d] xfs: mark reclaimed inodes invalid earlier
[5a90e53] xfs: xfs_iflush_cluster has range issues
[1942936] xfs: rename variables in xfs_iflush_cluster for clarity
[545c088] xfs: simplify inode reclaim tagging interfaces
[ad438c4] xfs: move reclaim tagging functions
[8b7a242] Merge branch 'xfs-4.7-writeback-bio' into for-next
[d6bd961] Merge branch 'xfs-4.7-trans-type-cleanup' into for-next
[5b911354] Merge branch 'xfs-4.7-optimise-inline-symlinks' into for-next
[a7792aa] Merge branch 'xfs-4.7-cleanup-attr-listent' into for-next
[2a4ad58] Merge branch 'xfs-4.7-misc-fixes' into for-next
[544ad71] Merge branch 'xfs-4.7-error-cfg' into for-next
[555b67e] Merge branch 'xfs-4.7-inode-reclaim' into for-next
Code Diffstat:
fs/xfs/libxfs/xfs_inode_fork.c | 27 ++--
fs/xfs/xfs_aops.c | 5 +-
fs/xfs/xfs_buf.c | 12 +-
fs/xfs/xfs_buf.h | 20 +++
fs/xfs/xfs_buf_item.c | 121 +++++++++++-------
fs/xfs/xfs_icache.c | 290 +++++++++++++++++++++++--------------------
fs/xfs/xfs_inode.c | 104 ++++++++++------
fs/xfs/xfs_mount.c | 22 +++-
fs/xfs/xfs_mount.h | 34 ++++++
fs/xfs/xfs_super.c | 28 ++---
fs/xfs/xfs_sysfs.c | 291 +++++++++++++++++++++++++++++++++++++++++++-
fs/xfs/xfs_sysfs.h | 3 +
fs/xfs/xfs_trace.h | 1 -
13 files changed, 702 insertions(+), 256 deletions(-)
--
Dave Chinner
david@fromorbit.com
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2016-05-20 1:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160520015330.GD26977@dastard \
--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