cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v2 0/6] Pre-pull patch posting (merge window)
Date: Mon,  9 Nov 2015 10:01:26 -0600	[thread overview]
Message-ID: <1447084892-30129-1-git-send-email-rpeterso@redhat.com> (raw)

Hi,

Here is a list of patches we've accumulated for GFS2 for the current upstream
merge window. I added one more patch regarding a serious block size problem.
There are only six patches this time:

1. A cleanup patch from Andreas to remove the gl_spin #define in favor
   of its value for the sake of clarity.
2. A fix from Andy Price to mark the inode dirty during fallocate.
3. A fix from Andy Price to set s_mode on mount failures to prevent
   a stack trace.
4. A patch from me to prevent a kernel BUG() in trans_add_meta/trans_add_data
   due to uninitialized storage.
5. A patch from me to protecting our freeing of the in-core directory
   hash table to prevent double-free.   
6. A fix for a page/block rounding problem that resulted in a metadata
   coherency problem when the block size != page size.

I've got a lot more patches in various stages of review and testing,
but I'm afraid they'll have to wait until the next merge window. So
next time we're likely to have a lot more.

Regards,

Bob Peterson
Red Hat File Systems

----------------------------------------------------------------

Andreas Gruenbacher (1):
  gfs2: Remove gl_spin define

Andrew Price (2):
  GFS2: fallocate: do not rely on file_update_time to mark the inode
    dirty
  GFS2: Set s_mode before parsing mount options

Bob Peterson (3):
  gfs2: Add missing else in trans_add_meta/data
  GFS2: Protect freeing directory hash table with i_lock spin_lock
  GFS2: Fix rgrp end rounding problem for bsize < page size

 Documentation/filesystems/gfs2-glocks.txt |  6 +--
 fs/gfs2/dir.c                             |  7 ++-
 fs/gfs2/file.c                            |  2 +-
 fs/gfs2/glock.c                           | 84 +++++++++++++++----------------
 fs/gfs2/glock.h                           |  4 +-
 fs/gfs2/glops.c                           | 10 ++--
 fs/gfs2/incore.h                          |  3 +-
 fs/gfs2/main.c                            |  2 +-
 fs/gfs2/ops_fstype.c                      |  4 +-
 fs/gfs2/rgrp.c                            |  9 ++--
 fs/gfs2/trans.c                           |  4 ++
 11 files changed, 73 insertions(+), 62 deletions(-)

-- 
2.4.3



             reply	other threads:[~2015-11-09 16:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09 16:01 Bob Peterson [this message]
2015-11-09 16:01 ` [Cluster-devel] [PATCH v2 1/6] GFS2: fallocate: do not rely on file_update_time to mark the inode dirty Bob Peterson
2015-11-09 16:01 ` [Cluster-devel] [PATCH v2 2/6] GFS2: Set s_mode before parsing mount options Bob Peterson
2015-11-09 16:01 ` [Cluster-devel] [PATCH v2 3/6] gfs2: Add missing else in trans_add_meta/data Bob Peterson
2015-11-09 16:01 ` [Cluster-devel] [PATCH v2 4/6] gfs2: Remove gl_spin define Bob Peterson
2015-11-09 16:01 ` [Cluster-devel] [PATCH v2 5/6] GFS2: Protect freeing directory hash table with i_lock spin_lock Bob Peterson
2015-11-09 16:01 ` [Cluster-devel] [PATCH v2 6/6] GFS2: Fix rgrp end rounding problem for bsize < page size Bob Peterson

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=1447084892-30129-1-git-send-email-rpeterso@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 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).