[PATCH v2] erofs: fix bio->bi_max_vecs behavior change
Gao Xiang
hsiangkao at redhat.com
Mon Mar 8 13:36:50 AEDT 2021
Hi Chao,
On Mon, Mar 08, 2021 at 09:29:30AM +0800, Chao Yu wrote:
> On 2021/3/6 12:04, Gao Xiang wrote:
> > From: Gao Xiang <hsiangkao at redhat.com>
> >
> > Martin reported an issue that directory read could be hung on the
> > latest -rc kernel with some certain image. The root cause is that
> > commit baa2c7c97153 ("block: set .bi_max_vecs as actual allocated
> > vector number") changes .bi_max_vecs behavior. bio->bi_max_vecs
> > is set as actual allocated vector number rather than the requested
> > number now.
> >
> > Let's avoid using .bi_max_vecs completely instead.
> >
> > Reported-by: Martin DEVERA <devik at eaxlabs.cz>
> > Signed-off-by: Gao Xiang <hsiangkao at redhat.com>
>
> Looks good to me, btw, it needs to Cc stable mailing list?
>
> Reviewed-by: Chao Yu <yuchao0 at huawei.com>
>
Thanks for your review. <= 5.11 kernels are not impacted.
For now, this only impacts 5.12-rc due to a bio behavior
change (see commit baa2c7c97153). So personally I think
just leave as it is is fine.
Thanks,
Gao Xiang
> Thanks,
>
More information about the Linux-erofs
mailing list