From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Pull request (fixes)
Date: Mon, 19 Aug 2013 10:26:08 +0100 [thread overview]
Message-ID: <1376904368.2679.9.camel@menhir> (raw)
Oops, forgot to sign this when I sent it first, so here is a signed copy of it.
Hi,
Please consider pulling the following changes,
Steve.
-----------------------------------------------------------------------------
Out of these five patches, the one for ensuring that the number of
revokes is not exceeded, and the one for checking the glock is not
already held in gfs2_getxattr are the two most important. The latter
can be triggered by selinux.
The other three patches are very small and fix mostly fairly
trivial issues.
------------------------------------------------------------------------------
The following changes since commit 47188d39b5deeebf41f87a02af1b3935866364cf:
Merge tag 'ext4_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4 (2013-07-14 21:47:51 -0700)
are available in the git repository at:
https://git.kernel.org/cgit/linux/kernel/git/steve/gfs2-3.0-fixes.git master
Benjamin Marzinski (1):
GFS2: don't overrun reserved revokes
Dan Carpenter (1):
GFS2: alloc_workqueue() doesn't return an ERR_PTR
Steven Whitehouse (2):
GFS2: Fix typo in gfs2_create_inode()
GFS2: Check for glock already held in gfs2_getxattr
Tejun Heo (1):
GFS2: WQ_NON_REENTRANT is meaningless and going away
fs/gfs2/glock.c | 8 ++++----
fs/gfs2/glops.c | 18 +++++++++++++-----
fs/gfs2/inode.c | 6 +++++-
fs/gfs2/main.c | 2 +-
4 files changed, 23 insertions(+), 11 deletions(-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20130819/7f97c4af/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Steven Whitehouse <swhiteho@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, cluster-devel@redhat.com
Subject: GFS2: Pull request (fixes)
Date: Mon, 19 Aug 2013 10:26:08 +0100 [thread overview]
Message-ID: <1376904368.2679.9.camel@menhir> (raw)
[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]
Oops, forgot to sign this when I sent it first, so here is a signed copy of it.
Hi,
Please consider pulling the following changes,
Steve.
-----------------------------------------------------------------------------
Out of these five patches, the one for ensuring that the number of
revokes is not exceeded, and the one for checking the glock is not
already held in gfs2_getxattr are the two most important. The latter
can be triggered by selinux.
The other three patches are very small and fix mostly fairly
trivial issues.
------------------------------------------------------------------------------
The following changes since commit 47188d39b5deeebf41f87a02af1b3935866364cf:
Merge tag 'ext4_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4 (2013-07-14 21:47:51 -0700)
are available in the git repository at:
https://git.kernel.org/cgit/linux/kernel/git/steve/gfs2-3.0-fixes.git master
Benjamin Marzinski (1):
GFS2: don't overrun reserved revokes
Dan Carpenter (1):
GFS2: alloc_workqueue() doesn't return an ERR_PTR
Steven Whitehouse (2):
GFS2: Fix typo in gfs2_create_inode()
GFS2: Check for glock already held in gfs2_getxattr
Tejun Heo (1):
GFS2: WQ_NON_REENTRANT is meaningless and going away
fs/gfs2/glock.c | 8 ++++----
fs/gfs2/glops.c | 18 +++++++++++++-----
fs/gfs2/inode.c | 6 +++++-
fs/gfs2/main.c | 2 +-
4 files changed, 23 insertions(+), 11 deletions(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-08-19 9:26 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 9:26 Steven Whitehouse [this message]
2013-08-19 9:26 ` GFS2: Pull request (fixes) Steven Whitehouse
2013-08-19 16:33 ` [Cluster-devel] " Linus Torvalds
2013-08-19 16:33 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2014-09-16 10:11 [Cluster-devel] " Steven Whitehouse
2014-07-18 11:21 Steven Whitehouse
2014-01-02 12:41 Steven Whitehouse
2013-11-22 10:39 Steven Whitehouse
2013-08-19 9:24 Steven Whitehouse
2013-06-04 15:40 Steven Whitehouse
2013-05-24 14:05 Steven Whitehouse
2013-04-05 10:34 Steven Whitehouse
2013-04-05 16:27 ` David Teigland
2013-04-05 16:51 ` Steven Whitehouse
2013-04-05 16:53 ` Linus Torvalds
2013-04-05 17:52 ` Steven Whitehouse
2013-01-28 10:31 Steven Whitehouse
2013-01-03 12:28 Steven Whitehouse
2012-11-07 10:58 Steven Whitehouse
2012-09-13 13:42 Steven Whitehouse
2012-04-11 10:21 Steven Whitehouse
2012-04-11 10:18 Steven Whitehouse
2012-02-28 11:49 Steven Whitehouse
2011-07-27 10:00 Steven Whitehouse
2011-07-14 15:16 Steven Whitehouse
2011-05-23 14:05 Steven Whitehouse
2011-04-19 9:13 Steven Whitehouse
2011-01-19 10:50 Steven Whitehouse
2010-11-29 13:42 Steven Whitehouse
2010-11-15 15:41 Steven Whitehouse
2010-09-17 13:59 Steven Whitehouse
2010-07-15 14:35 Steven Whitehouse
2010-05-25 8:51 Steven Whitehouse
2010-03-11 17:41 Steven Whitehouse
2010-02-12 11:37 Steven Whitehouse
2010-02-04 10:06 Steven Whitehouse
2010-02-02 10:07 [Cluster-devel] [GFS2] " Steven Whitehouse
2010-01-11 14:24 [Cluster-devel] GFS2: " Steven Whitehouse
2009-08-14 13:01 Steven Whitehouse
2009-07-30 13:45 [Cluster-devel] GFS2: Pre-pull patch posting (fixes) Steven Whitehouse
2009-07-30 13:02 ` [Cluster-devel] GFS2: Pull request (fixes) Steven Whitehouse
2009-04-23 13:13 Steven Whitehouse
2009-01-07 10:21 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=1376904368.2679.9.camel@menhir \
--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 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.