From: Bob Peterson <rpeterso@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: cluster-devel <cluster-devel@redhat.com>, linux-kernel@vger.kernel.org
Subject: GFS2: Pull request #2 (merge window)
Date: Thu, 12 Apr 2018 14:53:48 -0400 (EDT) [thread overview]
Message-ID: <221420024.18959486.1523559228057.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1349891308.18959471.1523559205878.JavaMail.zimbra@redhat.com>
Hi Linus,
Please consider pulling the following additional 3 patches for the GFS2
file system.
Regards,
Bob Peterson
----------------------------------------------------------------
The following changes since commit e241e3f2bf975788a1b70dff2eb5180ca395b28e:
Merge tag 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost (2018-04-11 18:58:27 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-4.17.fixes2
for you to fetch changes up to 3e7aafc39c59c639ebd5961f893743f076df9b4e:
GFS2: Minor improvements to comments and documentation (2018-04-12 10:07:51 -0700)
----------------------------------------------------------------
We decided to request the latest three patches to be merged into this
merge window while it's still open.
1. The first patch adds a new function to lockref: lockref_put_not_zero
2. The second patch fixes GFS2's glock dump code so it uses the new lockref
function. This fixes a problem whereby lock dumps could miss glocks.
3. I made a minor patch to update some comments and fix the lock ordering
text in our gfs2-glocks.txt Documentation file.
----------------------------------------------------------------
Andreas Gruenbacher (2):
lockref: Add lockref_put_not_zero
gfs2: Stop using rhashtable_walk_peek
Bob Peterson (1):
GFS2: Minor improvements to comments and documentation
Documentation/filesystems/gfs2-glocks.txt | 5 ++--
fs/gfs2/bmap.c | 2 +-
fs/gfs2/glock.c | 47 ++++++++++++++++++-------------
fs/gfs2/ops_fstype.c | 2 +-
include/linux/lockref.h | 1 +
lib/lockref.c | 28 ++++++++++++++++++
6 files changed, 62 insertions(+), 23 deletions(-)
next parent reply other threads:[~2018-04-12 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1349891308.18959471.1523559205878.JavaMail.zimbra@redhat.com>
2018-04-12 18:53 ` Bob Peterson [this message]
2012-01-13 10:04 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=221420024.18959486.1523559228057.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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
Powered by JetHome