From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@oss.sgi.com
Subject: [ANNOUNCE] xfs: for-next branch updated to 2e405cd
Date: Mon, 26 Sep 2016 10:49:17 +1000 [thread overview]
Message-ID: <20160926004917.GU340@dastard> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1869 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 includes a bunch of log recovery fixes
for v5 filesystems.
REMINDER: xfs@oss.sgi.com is going at the end of the month. Please
change your XFS list subscription to linux-xfs@vger.kernel.org,
otherwise things will go silent for you....
-Dave.
The new head of the for-next branch is commit:
2e405cd Merge branch 'xfs-4.9-log-recovery-fixes' into for-next
New Commits:
Brian Foster (5):
[12818d2] xfs: rework log recovery to submit buffers on LSN boundaries
[22db9af] xfs: pass current lsn to log recovery buffer validation
[040c52c] xfs: don't warn on buffers not being recovered due to LSN
[60a4a22] xfs: update metadata LSN in buffers during log recovery
[5cd9cee] xfs: log recovery tracepoints to track current lsn and buffer submission
Dave Chinner (3):
[292378e] xfs: remote attribute blocks aren't really userdata
[ddeb14f] xfs: quiesce the filesystem after recovery on readonly mount
[2e405cd] Merge branch 'xfs-4.9-log-recovery-fixes' into for-next
Code Diffstat:
fs/xfs/libxfs/xfs_alloc.c | 23 +++---
fs/xfs/libxfs/xfs_alloc.h | 17 ++++-
fs/xfs/libxfs/xfs_bmap.c | 41 +++++++----
fs/xfs/libxfs/xfs_bmap.h | 2 +-
fs/xfs/xfs_bmap_util.c | 2 +-
fs/xfs/xfs_extent_busy.c | 2 +-
fs/xfs/xfs_filestream.c | 9 ++-
fs/xfs/xfs_log_priv.h | 3 +-
fs/xfs/xfs_log_recover.c | 191 ++++++++++++++++++++++++++++++++++---------------
fs/xfs/xfs_mount.c | 14 ++++
fs/xfs/xfs_super.c | 2 +-
fs/xfs/xfs_super.h | 1 +
fs/xfs/xfs_trace.h | 39 ++++++++--
13 files changed, 248 insertions(+), 98 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
next reply other threads:[~2016-09-26 0:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 0:49 Dave Chinner [this message]
2016-09-30 9:57 ` [ANNOUNCE] xfs: for-next branch updated to 2e405cd Eryu Guan
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=20160926004917.GU340@dastard \
--to=david@fromorbit.com \
--cc=linux-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;
as well as URLs for NNTP newsgroup(s).