FROMGIT: erofs: fix bio->bi_max_vecs behavior change

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 baa2c7c9 ("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.

Link: https://lore.kernel.org/r/20210306040438.8084-1-hsiangkao@aol.com


Reported-by: Martin DEVERA <devik@eaxlabs.cz>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
[ Gao Xiang: note that <= 5.11 kernels are not impacted. ]
Signed-off-by: Gao Xiang <hsiangkao@redhat.com>

BUG=b:273658215
TEST=`tast run $DUT arc.Boot.vm`
TEST=`tast run $DUT arc.Playstore.vm`

(cherry picked from commit 1571cef7
 https://android.googlesource.com/kernel/common

 android13-5.10)

Change-Id: I53cdeeabc94ebbf7e097c2032daca8b5dfe4b4dc
Signed-off-by: Ryuichiro Chiba <chibar@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/4444990


Reviewed-by: Suleiman Souhlal <suleiman@chromium.org>
Reviewed-by: Sean Paul <sean@poorly.run>