All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Pull request (merge window)
Date: Thu, 17 Mar 2016 08:51:46 -0400 (EDT)	[thread overview]
Message-ID: <454051961.39163640.1458219106285.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <2094757318.39162844.1458219077321.JavaMail.zimbra@redhat.com>

Hi,

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

Bob Peterson

----------------------------------------------------------------
The following changes since commit 67990608c8b95d2b8ccc29932376ae73d5818727:

  Merge tag 'pm+acpi-4.5-rc1-1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm (2016-01-12 20:25:09 -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 73b462d2808d7cbca4d7886cf6aaed850640e6cd:

  GFS2: Eliminate parameter non_block on gfs2_inode_lookup (2016-03-15 10:46:50 -0400)

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

We only have six patches ready for this merge window.

- Arnd Bergmann contributed a patch that fixes an uninitialized variable
  warning.
- The second patch avoids a kernel panic due to referencing an iopen
  glock that may not be held, in an error path.
- The third patch fixes a rounding error that caused xfs_tests direct IO
  write "fsx" tests to fail on GFS2.
- The fourth patch tidies up the code path when glocks are being reused
  to recreate a dinode that was recently deleted.
- The fifth reverts an ages-old patch that should no longer be needed, and
  which interfered with the transition of dinodes from unlinked to free.
- And lastly, a patch to eliminate a function parameter that's not needed.

----------------------------------------------------------------
Arnd Bergmann (1):
      gfs2: avoid uninitialized variable warning

Bob Peterson (5):
      GFS2: Check if iopen is held when deleting inode
      GFS2: Fix direct IO write rounding error
      GFS2: Prevent delete work from occurring on glocks used for create
      GFS2: Don't filter out I_FREEING inodes anymore
      GFS2: Eliminate parameter non_block on gfs2_inode_lookup

 fs/gfs2/aops.c       |  2 +-
 fs/gfs2/dir.c        |  6 ++---
 fs/gfs2/export.c     |  2 +-
 fs/gfs2/glock.c      | 10 +++++++-
 fs/gfs2/incore.h     |  1 +
 fs/gfs2/inode.c      | 71 +++++++++-------------------------------------------
 fs/gfs2/inode.h      |  5 ++--
 fs/gfs2/ops_fstype.c |  2 +-
 fs/gfs2/super.c      | 26 +++++++++++--------
 9 files changed, 46 insertions(+), 79 deletions(-)



WARNING: multiple messages have this Message-ID (diff)
From: Bob Peterson <rpeterso@redhat.com>
To: torvalds@linux-foundation.org
Cc: cluster-devel <cluster-devel@redhat.com>, linux-kernel@vger.kernel.org
Subject: GFS2: Pull request (merge window)
Date: Thu, 17 Mar 2016 08:51:46 -0400 (EDT)	[thread overview]
Message-ID: <454051961.39163640.1458219106285.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <2094757318.39162844.1458219077321.JavaMail.zimbra@redhat.com>

Hi,

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

Bob Peterson

----------------------------------------------------------------
The following changes since commit 67990608c8b95d2b8ccc29932376ae73d5818727:

  Merge tag 'pm+acpi-4.5-rc1-1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm (2016-01-12 20:25:09 -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 73b462d2808d7cbca4d7886cf6aaed850640e6cd:

  GFS2: Eliminate parameter non_block on gfs2_inode_lookup (2016-03-15 10:46:50 -0400)

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

We only have six patches ready for this merge window.

- Arnd Bergmann contributed a patch that fixes an uninitialized variable
  warning.
- The second patch avoids a kernel panic due to referencing an iopen
  glock that may not be held, in an error path.
- The third patch fixes a rounding error that caused xfs_tests direct IO
  write "fsx" tests to fail on GFS2.
- The fourth patch tidies up the code path when glocks are being reused
  to recreate a dinode that was recently deleted.
- The fifth reverts an ages-old patch that should no longer be needed, and
  which interfered with the transition of dinodes from unlinked to free.
- And lastly, a patch to eliminate a function parameter that's not needed.

----------------------------------------------------------------
Arnd Bergmann (1):
      gfs2: avoid uninitialized variable warning

Bob Peterson (5):
      GFS2: Check if iopen is held when deleting inode
      GFS2: Fix direct IO write rounding error
      GFS2: Prevent delete work from occurring on glocks used for create
      GFS2: Don't filter out I_FREEING inodes anymore
      GFS2: Eliminate parameter non_block on gfs2_inode_lookup

 fs/gfs2/aops.c       |  2 +-
 fs/gfs2/dir.c        |  6 ++---
 fs/gfs2/export.c     |  2 +-
 fs/gfs2/glock.c      | 10 +++++++-
 fs/gfs2/incore.h     |  1 +
 fs/gfs2/inode.c      | 71 +++++++++-------------------------------------------
 fs/gfs2/inode.h      |  5 ++--
 fs/gfs2/ops_fstype.c |  2 +-
 fs/gfs2/super.c      | 26 +++++++++++--------
 9 files changed, 46 insertions(+), 79 deletions(-)

       reply	other threads:[~2016-03-17 12:51 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2094757318.39162844.1458219077321.JavaMail.zimbra@redhat.com>
2016-03-17 12:51 ` Bob Peterson [this message]
2016-03-17 12:51   ` GFS2: Pull request (merge window) Bob Peterson
     [not found] <2063498114.10752149.1552067836491.JavaMail.zimbra@redhat.com>
2019-03-08 17:58 ` [Cluster-devel] " 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] <1872743029.687446.1475513532790.JavaMail.zimbra@redhat.com>
2016-10-03 16:52 ` 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] <1243871936.8427302.1452623511952.JavaMail.zimbra@redhat.com>
2016-01-12 18:34 ` 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 [Cluster-devel] GFS2: Pull request (fixes) Steven Whitehouse
2012-10-01  9:09 ` [Cluster-devel] 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=454051961.39163640.1458219106285.JavaMail.zimbra@redhat.com \
    --to=rpeterso@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.