From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] gfs2: Remove dirty buffer warning from gfs2_releasepage
Date: Thu, 18 Aug 2016 11:32:04 -0400 (EDT) [thread overview]
Message-ID: <378893404.5778833.1471534324427.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1471527681-15004-1-git-send-email-agruenba@redhat.com>
----- Original Message -----
| Unlike what its documentation suggests, the releasepage address space
| operation can currently be called on dirty pages via shrink_active_list.
| This may eventually be changed when the remaining code relying on the
| current behavior has been fixed, but until then, it makes no sense to
| warn on dirty buffers in gfs2_releasepage.
|
| Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
| ---
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=1c185c02f454c47d573a17e3e7d8befb06f0d64d
Regards,
Bob Peterson
Red Hat File Systems
prev parent reply other threads:[~2016-08-18 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 13:41 [Cluster-devel] [PATCH] gfs2: Remove dirty buffer warning from gfs2_releasepage Andreas Gruenbacher
2016-08-18 15:32 ` 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=378893404.5778833.1471534324427.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 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.