public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: torvalds@linux-foundation.org
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: [GIT PULL] xfs: update for v4.1-rc6
Date: Sat, 30 May 2015 08:55:46 +1000	[thread overview]
Message-ID: <20150529225546.GF4316@dastard> (raw)

Hi Linus,

Can you please pull the fixes from the tag below? It's a little
larger than I'd like late in the release cycle, but all the fixes
are for regressions introduced in the 4.1-rc1 merge, or are needed
back in -stable kernels fairly quickly as they are filesystem
corruption or userspace visible correctness issues.

Thanks!

-Dave.

The following changes since commit 5ebe6afaf0057ac3eaeb98defd5456894b446d22:

  Linux 4.1-rc2 (2015-05-03 19:22:23 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git tags/xfs-for-linus-4.1-rc6

for you to fetch changes up to 22419ac9fe5e79483596cebdbd1d1209c18bac1a:

  xfs: fix broken i_nlink accounting for whiteout tmpfile inode (2015-05-29 08:14:55 +1000)

----------------------------------------------------------------
xfs: update for 4.1-rc6

Changes in this update:
o regression fix for new rename whiteout code
o regression fixes for new superblock generic per-cpu counter code
o fix for incorrect error return sign introduced in 3.17
o metadata corruption fixes that need to go back to -stable kernels

----------------------------------------------------------------
Brian Foster (1):
      xfs: fix broken i_nlink accounting for whiteout tmpfile inode

Dave Chinner (5):
      percpu_counter: batch size aware __percpu_counter_compare()
      xfs: inode and free block counters need to use __percpu_counter_compare
      xfs: extent size hints can round up extents past MAXEXTLEN
      xfs: xfs_attr_inactive leaves inconsistent attr fork state behind
      xfs: xfs_iozero can return positive errno

George Wang (1):
      xfs: use percpu_counter_read_positive for mp->m_icount

 fs/xfs/libxfs/xfs_attr_leaf.c  |    8 ++--
 fs/xfs/libxfs/xfs_attr_leaf.h  |    2 +-
 fs/xfs/libxfs/xfs_bmap.c       |   31 +++++++++------
 fs/xfs/libxfs/xfs_ialloc.c     |    9 +++--
 fs/xfs/xfs_attr_inactive.c     |   83 ++++++++++++++++++++++++----------------
 fs/xfs/xfs_file.c              |    2 +-
 fs/xfs/xfs_inode.c             |   22 ++++++-----
 fs/xfs/xfs_mount.c             |   34 +++++++++-------
 include/linux/percpu_counter.h |   13 ++++++-
 lib/percpu_counter.c           |    6 +--
 10 files changed, 127 insertions(+), 83 deletions(-)

-- 
Dave Chinner
david@fromorbit.com

                 reply	other threads:[~2015-05-29 22:56 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=20150529225546.GF4316@dastard \
    --to=david@fromorbit.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --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