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: fixes for 3.16-rc5
Date: Fri, 18 Jul 2014 09:37:50 +1000	[thread overview]
Message-ID: <20140717233750.GE20518@dastard> (raw)

Hi Linus,

Can you please pull the updates listed below? These are regression
fixes for issues recently introduced - the change in the stack
switch location is fairly important, so I've held off sending this
update until I was sure that it still addresses the stack usage
problem the original solved. So while the commits in the xfs tree
are recent, it has been under tested for several weeks now.

-Dave.

The following changes since commit a497c3ba1d97fc69c1e78e7b96435ba8c2cb42ee:

  Linux 3.16-rc2 (2014-06-21 19:02:54 -1000)

are available in the git repository at:

  git://oss.sgi.com/xfs/xfs.git tags/xfs-for-linus-3.16-rc5

for you to fetch changes up to 03e01349c654fbdea80d3d9b4ab599244eb55bb7:

  xfs: null unused quota inodes when quota is on (2014-07-15 07:28:41 +1000)

----------------------------------------------------------------
xfs: fixes for 3.15-rc5

Fixes for low memory perforamnce regressions and a quota inode handling
regression.

----------------------------------------------------------------
Dave Chinner (3):
      Revert "xfs: block allocation work needs to be kswapd aware"
      xfs: refine the allocation stack switch
      xfs: null unused quota inodes when quota is on

 fs/xfs/xfs_bmap.c      |    7 ++-----
 fs/xfs/xfs_bmap.h      |    4 +---
 fs/xfs/xfs_bmap_util.c |   53 -----------------------------------------------------
 fs/xfs/xfs_bmap_util.h |    4 ----
 fs/xfs/xfs_btree.c     |   82 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
 fs/xfs/xfs_iomap.c     |    3 +--
 fs/xfs/xfs_sb.c        |   25 +++++++++++++++++++++----
 7 files changed, 106 insertions(+), 72 deletions(-)


-- 
Dave Chinner
david@fromorbit.com

                 reply	other threads:[~2014-07-17 23:37 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=20140717233750.GE20518@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