From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [RHEL7 fs 0/3] gfs2: Fixes to "Implement iomap for block_map"
Date: Tue, 6 Feb 2018 19:31:49 +0100 [thread overview]
Message-ID: <20180206183152.4758-1-agruenba@redhat.com> (raw)
There are several regressions in commit "[fs] gfs2: Implement iomap for
block_map", which are fixed in mainline commit "Fixes to "Implement
iomap for block_map"".
Because mainline commit "Fixes to "Implement iomap for block_map""
depends on commit "gfs2: Clean up {lookup,fillup}_metapath", backport
that as well.
The regressions trigger a WARN_ON(iomap.length == 0) in iomap_apply in
mainline. This WARN_ON hasn't been backported to RHEL7 yet, so in order
to have a reasonable reproducer, backport that patch as well.
Andreas Gruenbacher (2):
gfs2: Clean up {lookup,fillup}_metapath
gfs2: Fixes to "Implement iomap for block_map"
Darrick J. Wong (1):
iomap: warn on zero-length mappings
fs/gfs2/bmap.c | 117 ++++++++++++++++++++++++++-------------------------------
fs/iomap.c | 2 +
2 files changed, 55 insertions(+), 64 deletions(-)
--
2.14.3
next reply other threads:[~2018-02-06 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 18:31 Andreas Gruenbacher [this message]
2018-02-06 18:31 ` [Cluster-devel] [RHEL7 fs 1/3] iomap: warn on zero-length mappings Andreas Gruenbacher
2018-02-06 18:31 ` [Cluster-devel] [RHEL7 fs 2/3] gfs2: Clean up {lookup, fillup}_metapath Andreas Gruenbacher
2018-02-06 18:31 ` [Cluster-devel] [RHEL7 fs 3/3] gfs2: Fixes to "Implement iomap for block_map" Andreas Gruenbacher
2018-02-06 18:41 ` [Cluster-devel] [RHEL7 fs 0/3] " Andreas Gruenbacher
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=20180206183152.4758-1-agruenba@redhat.com \
--to=agruenba@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).