On Wed, Aug 18, 2021 at 09:14:14AM +0900, Michael Paquier wrote:
> Sure. aef8948 gets down because of the performance impact. ccf4e27
> was a cleanup following up aef8948, that loses its meaning. And
> c3826f8 cannot be let alone because of the reasons why aef8948 was
> introduced, as it has no safety net for out-of-bound handling in the
> result buffer allocated.
And done, with such a description in the commit log.
--
Michael