From: Bob Peterson <rpeterso@redhat.com>
To: torvalds@linux-foundation.org
Cc: cluster-devel <cluster-devel@redhat.com>, linux-kernel@vger.kernel.org
Subject: GFS2: Please pull patch tagged gfs2-for-linus-4.14-rc3
Date: Mon, 25 Sep 2017 14:05:16 -0400 (EDT) [thread overview]
Message-ID: <796593472.14250010.1506362716362.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <2070450700.14249313.1506362668670.JavaMail.zimbra@redhat.com>
Hi Linus,
Would you please pull this one-off patch from Andreas Gruenbacher
that fixes a GFS2 regression? Thanks.
Bob Peterson
---
The following changes since commit 46c1e79fee417f151547aa46fae04ab06cb666f4:
Merge branch 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2017-09-13 12:24:20 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-for-linus-4.14-rc3
for you to fetch changes up to 10201655b085df8e000822e496e5d4016a167a36:
gfs2: Fix debugfs glocks dump (2017-09-25 12:32:33 -0500)
----------------------------------------------------------------
GFS2: Fix an old regression in GFS2's debugfs interface
This tag is meant for pulling a patch called "gfs2: Fix
debugfs glocks dump" which fixes a regression introduced
by commit 88ffbf3e03. The regression caused the glock
dump in debugfs to not report all the glocks, which makes
debugging extremely difficult.
----------------------------------------------------------------
Andreas Gruenbacher (1):
gfs2: Fix debugfs glocks dump
fs/gfs2/glock.c | 14 +++++---------
1 file changed, 5 insertions(+), 9 deletions(-)
parent reply other threads:[~2017-09-25 18:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <2070450700.14249313.1506362668670.JavaMail.zimbra@redhat.com>]
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=796593472.14250010.1506362716362.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