public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfs: for-next branch updated to 6f97077ff6ef
Date: Mon, 10 Oct 2016 23:44:20 +1100	[thread overview]
Message-ID: <20161010124420.GB23194@dastard> (raw)

[-- Attachment #1: Type: text/plain, Size: 1214 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 with a few reflink fixes from Darrick.

-Dave

The new head of the for-next branch is commit:

6f97077ff6ef xfs: rework refcount cow recovery error handling

New Commits:

Darrick J. Wong (7):
      [63646fc58d66] xfs: check inode reflink flag before calling reflink functions
      [024adf487022] xfs: reduce stack usage of _reflink_clear_inode_flag
      [97a1b87ea7b2] xfs: remove isize check from unshare operation
      [93fed47013b3] xfs: fix label inaccuracies
      [9780643cde26] xfs: fix error initialization
      [1987fd743415] xfs: clear reflink flag if setting realtime flag
      [6f97077ff6ef] xfs: rework refcount cow recovery error handling


Code Diffstat:

 fs/xfs/libxfs/xfs_refcount.c | 20 +++++++--------
 fs/xfs/xfs_file.c            |  8 +++---
 fs/xfs/xfs_ioctl.c           |  4 +--
 fs/xfs/xfs_reflink.c         | 64 ++++++++++++++++++-----------------------------
 fs/xfs/xfs_super.c           | 12 +++++----
 5 files changed, 47 insertions(+), 61 deletions(-)
-- 
Dave Chinner
david@fromorbit.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

                 reply	other threads:[~2016-10-10 12:44 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=20161010124420.GB23194@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