cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2] Pull request
Date: Fri, 10 Oct 2008 09:05:19 +0100	[thread overview]
Message-ID: <1223625919.3493.4.camel@localhost.localdomain> (raw)

Hi,

Please consider pulling the following changes. There have been no changes since
the patches were posted to lkml on Sept 26th.

Steve.

The following changes since commit 30a2f3c60a84092c8084dfe788b710f8d0768cd4:
  Linus Torvalds (1):
        Linux 2.6.27-rc3

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-2.6-nmw.git master

Abhijith Das (1):
      GFS2: GFS2 will panic if you misspell any mount options

Bob Peterson (2):
      GFS2: rm on multiple nodes causes panic
      GFS2: Direct IO write at end of file error

Julien Brunel (1):
      GFS2: Use an IS_ERR test rather than a NULL test

Steven Whitehouse (8):
      GFS2: Fix debugfs glock file iterator
      GFS2: Fix metafs mounts
      GFS2: Fix & clean up GFS2 rename
      GFS2: Fix race relating to glock min-hold time
      GFS2: The war on bloat
      GFS2: high time to take some time over atime
      GFS2: Add UUID to GFS2 sb
      GFS2: Support for I/O barriers

 fs/gfs2/glock.c             |   15 +-
 fs/gfs2/glock.h             |    1 -
 fs/gfs2/incore.h            |   38 ++--
 fs/gfs2/inode.c             |  159 +-----------
 fs/gfs2/inode.h             |    2 -
 fs/gfs2/log.c               |   21 ++-
 fs/gfs2/mount.c             |    7 +
 fs/gfs2/ops_address.c       |   18 +-
 fs/gfs2/ops_file.c          |   16 +-
 fs/gfs2/ops_fstype.c        |  578 +++++++++++++++++++++++++++++--------------
 fs/gfs2/ops_inode.c         |  127 ++++++++---
 fs/gfs2/ops_super.c         |  108 ++++++--
 fs/gfs2/super.c             |  340 -------------------------
 fs/gfs2/super.h             |    6 -
 fs/gfs2/sys.c               |   11 -
 include/linux/gfs2_ondisk.h |    6 +-
 16 files changed, 654 insertions(+), 799 deletions(-)




             reply	other threads:[~2008-10-10  8:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10  8:05 Steven Whitehouse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-05-08 11:48 [Cluster-devel] GFS2: Pull Request Andreas Gruenbacher
2019-05-08 17:55 ` Linus Torvalds
2019-05-08 18:06   ` Linus Torvalds
2019-05-08 20:17     ` Andreas Gruenbacher
2019-05-08 20:21       ` Linus Torvalds
2019-05-08 20:58       ` Jonathan Corbet
2019-05-08 21:05         ` Linus Torvalds
2019-05-08 21:50           ` Jonathan Corbet
2010-05-18  8:38 [Cluster-devel] GFS2: Pull request Steven Whitehouse
2010-03-02 11:03 Steven Whitehouse
2009-12-03 15:01 Steven Whitehouse
2009-09-14  8:08 Steven Whitehouse
2009-06-11 10:51 Steven Whitehouse
2009-04-15 11:26 Steven Whitehouse
2009-03-24 12:20 Steven Whitehouse
2009-01-05  9:34 Steven Whitehouse
2008-07-14 16:03 [Cluster-devel] [GFS2] " Steven Whitehouse
2008-06-24 21:12 Steven Whitehouse
2008-05-20  9:12 [Cluster-devel] [GFS2] Pre-pull patch posting (bug fixes) swhiteho
2008-05-20 10:05 ` [Cluster-devel] [GFS2] Pull request Steven Whitehouse
2008-04-18 16:53 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=1223625919.3493.4.camel@localhost.localdomain \
    --to=swhiteho@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 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).