Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 2d29f6b96d8f gfs2: Fix loop in gfs2_rbm_find.
The bot has tested the following trees: v4.20.6, v4.19.19, v4.14.97, v4.9.154,
v4.4.172, v3.18.133.
v4.20.6: Build OK!
v4.19.19: Fail
- Original Message -
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: 2d29f6b96d8f gfs2: Fix loop in gfs2_rbm_find.
>
> The bot has tested the following trees: v4.20.5, v4.19.18, v4.14.96,
> v4.9.153, v4.4.172,
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 2d29f6b96d8f gfs2: Fix loop in gfs2_rbm_find.
The bot has tested the following trees: v4.20.5, v4.19.18, v4.14.96, v4.9.153,
v4.4.172, v3.18.133.
v4.20.5: Build OK!
v4.19.18: Fail
- Original Message -
> - Original Message -
> > The fix from commit 2d29f6b96d8f introduced an unexpected performance
> > regression when allocating blocks. Fix by rewriting the overly
> > complicated wrap-around logic in gfs2_rbm_find in a more reasonable way.
> > Discovered and v
- Original Message -
> The fix from commit 2d29f6b96d8f introduced an unexpected performance
> regression when allocating blocks. Fix by rewriting the overly
> complicated wrap-around logic in gfs2_rbm_find in a more reasonable way.
> Discovered and verified with iozone.
>
> Fixes: 2d29f6
On Tue, 4 Dec 2018 at 21:22, Andreas Gruenbacher wrote:
>
> In gfs2_rbm_find, fix the resource group wrap-around logic that commit
> e579ed4f44 broke. Without this fix, gfs2_rbm_find can end up in an
> infinite loop in the worst case.
After some more review, it seems that the current mechanism o
