gfs2: Revert "Fix loop in gfs2_rbm_find"
authorAndreas Gruenbacher <agruenba@redhat.com>
Wed, 30 Jan 2019 20:30:36 +0000 (21:30 +0100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 6 Feb 2019 16:30:13 +0000 (17:30 +0100)
commit8b9be9db8a2ac5ec2046cc95df35487e5aaa136c
tree12fc2badc5ec9deab7f5292f0fdb04f793b782aa
parent83c22cd104b2480db491bc8252512ae958833467
gfs2: Revert "Fix loop in gfs2_rbm_find"

commit e74c98ca2d6ae4376cc15fa2a22483430909d96b upstream.

This reverts commit 2d29f6b96d8f80322ed2dd895bca590491c38d34.

It turns out that the fix can lead to a ~20 percent performance regression
in initial writes to the page cache according to iozone.  Let's revert this
for now to have more time for a proper fix.

Cc: stable@vger.kernel.org # v3.13+
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
Signed-off-by: Bob Peterson <rpeterso@redhat.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/gfs2/rgrp.c