From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] gfs2: Fixes to "Implement iomap for block_map" (2)
Date: Mon, 5 Mar 2018 08:51:58 -0500 (EST) [thread overview]
Message-ID: <980669705.7898074.1520257918575.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20180305131208.16623-1-agruenba@redhat.com>
----- Original Message -----
| It turns out that commit 3229c18c0d6b2 'Fixes to "Implement iomap for
| block_map"' introduced another bug in gfs2_iomap_begin that can cause
| gfs2_block_map to set bh->b_size of an actual buffer to 0. This can
| lead to arbitrary incorrect behavior including crashes or disk
| corruption. Revert the incorrect part of that commit.
|
| 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/fs/gfs2?h=for-next&id=dc49cacbdc4eecae05713c03e3ab6ac0b7c06c1c
Regards,
Bob Peterson
Red Hat File Systems
prev parent reply other threads:[~2018-03-05 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 13:12 [Cluster-devel] [PATCH] gfs2: Fixes to "Implement iomap for block_map" (2) Andreas Gruenbacher
2018-03-05 13:51 ` 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=980669705.7898074.1520257918575.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.