GFS2: Pull request (merge window)

GFS2: Pull request (merge window)

[Bob Peterson]

Hi,

Please consider pulling the following changes for the GFS2 file system.

Regards,

Bob Peterson

----------------------------------------------------------------
The following changes since commit f4a3ae9308e34bcd704325a08879b2c1cfb74686:

  GFS2: Use average srttb value in congestion calculations (2015-04-24 07:57:08 -0500)

are available in the git repository at:

  gitolite@gitolite.kernel.org:/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-merge-window

for you to fetch changes up to 39b0f1e9290880a6c905f639e7db6b646e302a4f:

  GFS2: Don't brelse rgrp buffer_heads every allocation (2015-06-19 07:40:22 -0500)

----------------------------------------------------------------
GFS2: merge window

Here is a list of patches we've accumulated for GFS2 for the current upstream
merge window. We have a good mixture this time. Here are some of the features:

1. Fix a problem with RO mounts writing to the journal.
2. Further improvements to quotas on GFS2.
3. Added support for rename2 and RENAME_EXCHANGE on GFS2.
4. Increase performance by making glock lru_list less of a bottleneck.
5. Increase performance by avoiding unnecessary buffer_head releases.
6. Increase performance by using average glock round trip time from all CPUs.
7. Fixes for some compiler warnings and minor white space issues.
8. Other misc. bug fixes

----------------------------------------------------------------
Abhi Das (5):
      gfs2: handle NULL rgd in set_rgrp_preferences
      gfs2: fix quota updates on block boundaries
      gfs2: limit quota log messages
      gfs2: s64 cast for negative quota value
      gfs2: Don't support fallocate on jdata	files

Antonio Ospite (1):
      GFS2: inode.c: indent with TABs, not spaces

Benjamin Marzinski (3):
      GFS2: mark the journal idle to fix ro mounts
      GFS2: add support for rename2 and RENAME_EXCHANGE
      GFS2: make sure S_NOSEC flag isn't overwritten

Bob Peterson (3):
      GFS2: Average in only non-zero round-trip times for congestion stats
      GFS2: Don't add all glocks to the lru
      GFS2: Don't brelse rgrp buffer_heads every allocation

Fabian Frederick (3):
      gfs2: convert simple_str to kstr
      gfs2: kerneldoc warning fixes
      gfs2: fix shadow warning in gfs2_rbm_find()

 fs/gfs2/aops.c       |  12 ++-
 fs/gfs2/file.c       |   4 +-
 fs/gfs2/glock.c      |   3 +-
 fs/gfs2/glops.c      |  20 +++--
 fs/gfs2/incore.h     |   2 +
 fs/gfs2/inode.c      | 211 +++++++++++++++++++++++++++++++++++++++++++++-----
 fs/gfs2/ops_fstype.c |   1 +
 fs/gfs2/quota.c      | 212 +++++++++++++++++++++++++++++++--------------------
 fs/gfs2/rgrp.c       |  41 +++++++---
 fs/gfs2/rgrp.h       |   1 +
 fs/gfs2/sys.c        |  66 +++++++++++-----
 11 files changed, 429 insertions(+), 144 deletions(-)

GFS2 pull request for this merge window delayed a couple days

[Bob Peterson]

Hi,

I just wanted to give everyone (especially Linus) a heads-up on this.
I've been collecting patches for the GFS2 file system's for-next
branch. The biggest change this time revolves around allowing GFS2
to use rhashtable for its glocks, providing far greater scalability.

Since the patch was posted to cluster-devel, various people (especially
Andreas G) posted a few small correction and cleanup patches. Rather than
giving Linus a big pile of messy patches, I opted to combine them into
one proper patch (doing things "the right way") plus the other five patches
I had already queued. Unfortunately, this was all done just as Stephen
Rothwell sent out his email not to push any more patches to linux-next,
which left me in limbo. I asked Stephen his advice, and based on that,
we decided to:

1. Push the "proper" patch set to for-next today.
2. Give linux-next two days to settle with the six new patches.
3. Then send the formal request to pull the patches for the merge window.

I just wanted to let everyone know why our patch pull request is delayed.

BTW, this six-patch set has already been posted to cluster-devel for
review and been signed off last Wednesday. All of them are pretty much
confined to GFS2 (except for new calls to rhashtable functions) so
hopefully this is just a formality. Sorry for the delay.

Regards,

Bob Peterson
GFS2 Maintainer