linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: cluster-devel <cluster-devel@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: GFS2: Pull request (merge window)
Date: Tue, 12 Jan 2016 13:34:30 -0500 (EST)	[thread overview]
Message-ID: <652861169.8428397.1452623670711.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1243871936.8427302.1452623511952.JavaMail.zimbra@redhat.com>

Hi,

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

Bob Peterson

----------------------------------------------------------------
The following changes since commit 42d4ebb42a17754d2e8344dc1aa486119671d0eb:

  Merge git://www.linux-watchdog.org/linux-watchdog (2015-11-10 10:11:12 -0800)

are available in the git repository at:

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

for you to fetch changes up to a93a99838248bdab49db2eaac00236847670bc7f:

  gfs2: fix flock panic issue (2015-12-22 08:06:08 -0600)

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

Here is a list of patches we've accumulated for GFS2 for the current upstream
merge window. Last window's set was short, but I warned that this one would
be bigger, and so it is. We've got 19 patches:

- A patch from Abhi Das to propagate the GFS2_DIF_SYSTEM bit so that newly
  added journals don't get flagged, deleted, and recreated by fsck.gfs2.
- Two patches from Andreas Gruenbacher to improve GFS2 performance where
  extended attributes are involved.
- A patch from Andy Price to fix a suspicious rcu dereference error.
- Two patches from Ben Marzinski that rework how GFS2's NFS cookies are
  managed. This fixes readdir problems with nfs-over-gfs2.
- A patch from Ben Marzinski that fixes a race in unmounting GFS2.
- A set of four patches from me to move the resource group reservations
  inside the gfs2 inode to improve performance and fix a bug whereby
  get_write_access improperly prevented some operations like chown.
- A patch from me to spinlock-protect the setting of system statfs file data.
  This was causing small discrepancies between df and du.
- A patch from me to reintroduce a timeout while clearing glocks which was
  accidentally dropped some time ago.
- A patch from me to wait for iopen glock dequeues in order to improve
  deleting of files that were unlinked from a different cluster node.
- A patch from me to ensure metadata address spaces get truncated when an
  inode is evicted.
- A patch from me to fix a bug in which a memory leak could occur in some
  error cases when inodes were trying to be created.
- A patch to consistently use iopen glocks to transition from the unlinked
  state to the deleted state.
- A patch to fix a glock reference count error when inode creation fails.
- A patch from Junxiao Bi to fix an flock panic.
- A patch from Markus Elfring that removes an unnecessary if.

----------------------------------------------------------------
Abhi Das (1):
      gfs2: Automatically set GFS2_DIF_SYSTEM flag on system files

Andreas Gruenbacher (2):
      gfs2: Extended attribute readahead
      gfs2: Extended attribute readahead optimization

Andrew Price (1):
      GFS2: Use rht_for_each_entry_rcu in glock_hash_walk

Benjamin Marzinski (3):
      gfs2: keep offset when splitting dir leaf blocks
      gfs2: change gfs2 readdir cookie
      gfs2: clear journal live bit in	gfs2_log_flush

Bob Peterson (10):
      GFS2: Extract quota data from reservations structure (revert 5407e24)
      GFS2: Make rgrp reservations part of the gfs2_inode structure
      GFS2: Reduce size of incore inode
      GFS2: Update master statfs buffer with sd_statfs_spin locked
      GFS2: Reintroduce a timeout in function gfs2_gl_hash_clear
      GFS2: Wait for iopen glock dequeues
      GFS2: Truncate address space mapping when deleting an inode
      GFS2: Release iopen glock in gfs2_create_inode error cases
      GFS2: Always use iopen glock for gl_deletes
      GFS2: Don't do glock put on when inode creation fails

Junxiao Bi (1):
      gfs2: fix flock panic issue

Markus Elfring (1):
      GFS2: Delete an unnecessary check before the function call "iput"

 fs/gfs2/aops.c                   |   2 +-
 fs/gfs2/bmap.c                   |  13 +--
 fs/gfs2/dir.c                    | 175 ++++++++++++++++++++++++++++++---------
 fs/gfs2/file.c                   |  34 ++++----
 fs/gfs2/glock.c                  |  18 ++--
 fs/gfs2/glock.h                  |  26 +++---
 fs/gfs2/incore.h                 |  23 +++--
 fs/gfs2/inode.c                  |  48 +++++------
 fs/gfs2/log.c                    |   3 +
 fs/gfs2/main.c                   |  16 ++--
 fs/gfs2/meta_io.c                |  82 ++++++++++++++++--
 fs/gfs2/meta_io.h                |   2 +-
 fs/gfs2/ops_fstype.c             |   6 +-
 fs/gfs2/quota.c                  | 117 +++++++++++++++++---------
 fs/gfs2/quota.h                  |   2 +
 fs/gfs2/rgrp.c                   |  57 +++++--------
 fs/gfs2/rgrp.h                   |   6 +-
 fs/gfs2/super.c                  |  43 ++++++----
 fs/gfs2/util.c                   |   2 +-
 fs/gfs2/util.h                   |   2 +-
 fs/gfs2/xattr.c                  |  10 +--
 include/uapi/linux/gfs2_ondisk.h |   9 +-
 22 files changed, 452 insertions(+), 244 deletions(-)

       reply	other threads:[~2016-01-12 18:34 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1243871936.8427302.1452623511952.JavaMail.zimbra@redhat.com>
2016-01-12 18:34 ` Bob Peterson [this message]
     [not found] <2063498114.10752149.1552067836491.JavaMail.zimbra@redhat.com>
2019-03-08 17:58 ` GFS2: Pull request (merge window) Bob Peterson
     [not found] <180051537.56890898.1545229879645.JavaMail.zimbra@redhat.com>
2018-12-19 14:31 ` Bob Peterson
     [not found] <1929897739.23623737.1540322729596.JavaMail.zimbra@redhat.com>
2018-10-23 19:26 ` Bob Peterson
2018-10-24 16:35   ` Linus Torvalds
2018-10-24 16:41     ` Bob Peterson
     [not found] <1772901878.39899227.1528134744434.JavaMail.zimbra@redhat.com>
2018-06-04 17:53 ` Bob Peterson
     [not found] <242799785.15741010.1522776740239.JavaMail.zimbra@redhat.com>
2018-04-03 17:32 ` Bob Peterson
     [not found] <2035999397.5567269.1517410350526.JavaMail.zimbra@redhat.com>
2018-01-31 14:54 ` Bob Peterson
     [not found] <800692691.31850756.1510678641181.JavaMail.zimbra@redhat.com>
2017-11-14 16:57 ` Bob Peterson
2017-11-14 17:17   ` Bob Peterson
     [not found] <1332965725.6958432.1504544624096.JavaMail.zimbra@redhat.com>
2017-09-04 17:05 ` Bob Peterson
     [not found] <2018468119.28735933.1499259957760.JavaMail.zimbra@redhat.com>
2017-07-05 13:08 ` Bob Peterson
     [not found] <909713995.4565875.1494016018520.JavaMail.zimbra@redhat.com>
2017-05-05 20:28 ` Bob Peterson
2017-05-05 21:07   ` Linus Torvalds
     [not found] <1526627784.3659456.1493822813354.JavaMail.zimbra@redhat.com>
2017-05-03 16:41 ` Bob Peterson
     [not found] <468087826.25173671.1487684421990.JavaMail.zimbra@redhat.com>
2017-02-21 13:41 ` Bob Peterson
     [not found] <603920106.687778.1475513554626.JavaMail.zimbra@redhat.com>
2016-10-03 16:55 ` Bob Peterson
     [not found] <404724578.17300814.1469208769730.JavaMail.zimbra@redhat.com>
2016-07-22 17:33 ` Bob Peterson
     [not found] <2074855986.8621406.1463772170266.JavaMail.zimbra@redhat.com>
2016-05-20 19:23 ` Bob Peterson
     [not found] <2094757318.39162844.1458219077321.JavaMail.zimbra@redhat.com>
2016-03-17 12:51 ` Bob Peterson
     [not found] <337313427.7367463.1447086799887.JavaMail.zimbra@redhat.com>
2015-11-09 16:45 ` Bob Peterson
     [not found] <987432592.26261269.1441889826020.JavaMail.zimbra@redhat.com>
2015-09-10 13:19 ` Bob Peterson
     [not found] <1946368926.25134466.1435330524247.JavaMail.zimbra@redhat.com>
2015-06-26 14:56 ` Bob Peterson
     [not found] <1305736412.15685734.1429033600005.JavaMail.zimbra@redhat.com>
2015-04-14 17:47 ` Bob Peterson
2015-04-14 23:16   ` Linus Torvalds
2015-04-15  7:34     ` Steven Whitehouse
2015-04-14 23:19   ` Linus Torvalds
2015-04-15 12:09     ` Bob Peterson
2015-02-10 11:04 Steven Whitehouse
  -- strict thread matches above, loose matches on Subject: below --
2014-12-08 18:26 Steven Whitehouse
2014-10-08 19:25 Steven Whitehouse
2014-06-04  9:33 Steven Whitehouse
2014-04-01 23:15 Steven Whitehouse
2014-04-04 21:52 ` Linus Torvalds
2014-04-07  9:31   ` Steven Whitehouse
2014-01-20 19:15 Steven Whitehouse
2013-11-05 15:39 Steven Whitehouse
2013-09-09  9:22 Steven Whitehouse
2013-07-01 15:20 Steven Whitehouse
2013-04-29 11:08 Steven Whitehouse
2013-02-19 16:38 Steven Whitehouse
2012-12-11 10:39 Steven Whitehouse
2012-09-13 13:42 GFS2: Pull request (fixes) Steven Whitehouse
2012-10-01  9:09 ` GFS2: Pull request (merge window) Steven Whitehouse
2012-07-23 14:59 Steven Whitehouse
2012-08-03  1:22 ` Linus Torvalds
2012-08-03 10:18   ` Steven Whitehouse
2012-08-03 16:16     ` Linus Torvalds
2012-05-21  8:17 Steven Whitehouse
2012-03-20 16:10 Steven Whitehouse
2012-01-06 12:09 Steven Whitehouse
2011-10-25  8:41 Steven Whitehouse
2011-07-22 12:08 Steven Whitehouse
2011-05-20  8:14 Steven Whitehouse
2011-03-16 13:55 Steven Whitehouse
2011-01-05 10:22 Steven Whitehouse
2010-10-21  9:43 Steven Whitehouse
2010-08-03  9:06 Steven Whitehouse

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=652861169.8428397.1452623670711.JavaMail.zimbra@redhat.com \
    --to=rpeterso@redhat.com \
    --cc=cluster-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).