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 0/9] GFS2: Pre-pull patch posting (merge window)
Date: Mon, 13 Apr 2015 10:10:22 -0500	[thread overview]
Message-ID: <1428937831-690-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. Most of the patches fix GFS2 quotas, which were not properly
enforced. There's another that adds me as a GFS2 co-maintainer, and a
couple patches that fix a kernel panic doing splice_write on GFS2 as well
as a few correctness patches.

Regards,

Bob Peterson
Red Hat File Systems

----------------------------------------------------------------
Abhi Das (4):
  gfs2: perform quota checks against allocation parameters
  gfs2: allow quota_check and inplace_reserve to return available blocks
  gfs2: allow fallocate to max out quotas/fs efficiently
  gfs2: fix quota refresh race in do_glock()

Andreas Gruenbacher (1):
  GFS2: gfs2_set_acl(): Cache "no acl" as well

Bob Peterson (3):
  Add myself (Bob Peterson) as a maintainer of GFS2
  GFS2: Allocate reservation during splice_write
  GFS2: Move gfs2_file_splice_write outside of #ifdef

Chengyu Song (1):
  gfs2: incorrect check for debugfs returns

 MAINTAINERS      |   4 +--
 fs/gfs2/acl.c    |   6 +---
 fs/gfs2/aops.c   |   6 ++--
 fs/gfs2/bmap.c   |   2 +-
 fs/gfs2/file.c   | 101 ++++++++++++++++++++++++++++++++++++++-----------------
 fs/gfs2/glock.c  |  47 +++++++++++++++-----------
 fs/gfs2/incore.h |   4 ++-
 fs/gfs2/inode.c  |  18 +++++-----
 fs/gfs2/quota.c  |  62 ++++++++++++++++++++++++----------
 fs/gfs2/quota.h  |   8 +++--
 fs/gfs2/rgrp.c   |  20 ++++++++---
 fs/gfs2/rgrp.h   |   3 +-
 fs/gfs2/xattr.c  |   2 +-
 13 files changed, 186 insertions(+), 97 deletions(-)

-- 
1.9.3



             reply	other threads:[~2015-04-13 15:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 15:10 Bob Peterson [this message]
2015-04-13 15:10 ` [Cluster-devel] [PATCH 1/9] Add myself (Bob Peterson) as a maintainer of GFS2 Bob Peterson
2015-04-13 15:10 ` [Cluster-devel] [PATCH 2/9] GFS2: gfs2_set_acl(): Cache "no acl" as well Bob Peterson
2015-04-13 15:10 ` [Cluster-devel] [PATCH 3/9] GFS2: Allocate reservation during splice_write Bob Peterson
2015-04-13 15:10 ` [Cluster-devel] [PATCH 4/9] GFS2: Move gfs2_file_splice_write outside of #ifdef Bob Peterson
2015-04-13 15:10 ` [Cluster-devel] [PATCH 5/9] gfs2: perform quota checks against allocation parameters Bob Peterson
2015-04-13 15:10 ` [Cluster-devel] [PATCH 6/9] gfs2: allow quota_check and inplace_reserve to return available blocks Bob Peterson
2015-04-13 15:10 ` [Cluster-devel] [PATCH 7/9] gfs2: allow fallocate to max out quotas/fs efficiently Bob Peterson
2015-04-13 15:10 ` [Cluster-devel] [PATCH 8/9] gfs2: incorrect check for debugfs returns Bob Peterson
2015-04-13 15:10 ` [Cluster-devel] [PATCH 9/9] gfs2: fix quota refresh race in do_glock() Bob Peterson
  -- strict thread matches above, loose matches on Subject: below --
2016-05-20 16:22 [Cluster-devel] [PATCH 0/9] GFS2: Pre-pull patch posting (merge window) Bob Peterson
2017-05-03 13:45 Bob Peterson
2018-04-02 15:44 Bob Peterson
2018-06-04 16:29 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=1428937831-690-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).