From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] gfs2: fix to detect failure of register_shrinker
Date: Wed, 21 Sep 2016 13:36:08 -0400 (EDT) [thread overview]
Message-ID: <1813719612.1511572.1474479368722.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1474299961-17951-1-git-send-email-chao@kernel.org>
----- Original Message -----
| From: Chao Yu <yuchao0@huawei.com>
|
| register_shrinker can fail after commit 1d3d4437eae1 ("vmscan: per-node
| deferred work"), we should detect the failure of it, otherwise we may
| fail to register shrinker after gfs2 module was been inited successfully.
|
| Signed-off-by: Chao Yu <yuchao0@huawei.com>
| ---
| fs/gfs2/glock.c | 8 +++++++-
| fs/gfs2/main.c | 4 +++-
| 2 files changed, 10 insertions(+), 2 deletions(-)
|
Hi,
Thanks. This is now applied to the for-next branch of the linux-gfs2 tree:
https://git.kernel.org/cgit/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=e0d735c1cc2749598f2d29f60f9a16658fd96ae9
Regards,
Bob Peterson
Red Hat File Systems
prev parent reply other threads:[~2016-09-21 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 15:46 [Cluster-devel] [PATCH] gfs2: fix to detect failure of register_shrinker Chao Yu
2016-09-21 17: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=1813719612.1511572.1474479368722.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).