From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] gfs2: Fix debugfs glocks dump
Date: Tue, 19 Sep 2017 08:36:08 -0400 (EDT) [thread overview]
Message-ID: <1536743131.11984428.1505824568754.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170919091617.18094-1-agruenba@redhat.com>
----- Original Message -----
| The switch to rhashtables (commit 88ffbf3e03) broke the debugfs glock
| dump (/sys/kernel/debug/gfs2/<device>/glocks) for dumps bigger than a
| single buffer: the right function for restarting an rhashtable iteration
| from the beginning of the hash table is rhashtable_walk_enter;
| rhashtable_walk_stop + rhashtable_walk_start will just resume from the
| current position.
|
| Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
| ---
Hi,
Thanks. This is now pushed to the for-next branch of the linux-gfs2 tree:
https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git/commit/?h=for-next&id=fdc47b4f0c2381d1dddeec7fffad0382ea1b9fcb
Regards,
Bob Peterson
Red Hat File Systems
prev parent reply other threads:[~2017-09-19 12:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 9:16 [Cluster-devel] [PATCH] gfs2: Fix debugfs glocks dump Andreas Gruenbacher
2017-09-19 12:36 ` Bob Peterson [this message]
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=1536743131.11984428.1505824568754.JavaMail.zimbra@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).