From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bob Peterson Date: Mon, 5 Mar 2018 08:51:58 -0500 (EST) Subject: [Cluster-devel] [PATCH] gfs2: Fixes to "Implement iomap for block_map" (2) In-Reply-To: <20180305131208.16623-1-agruenba@redhat.com> References: <20180305131208.16623-1-agruenba@redhat.com> Message-ID: <980669705.7898074.1520257918575.JavaMail.zimbra@redhat.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit ----- 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 | --- 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