gfs2: Fix inode height consistency check

stable inclusion
from stable-v5.10.181
commit 4c2c8f959984e8dbbfdb6441b33fb72609eaefc0
category: bugfix
bugzilla: https://gitee.com/openeuler/kernel/issues/I8GJZJ

Reference: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4c2c8f959984e8dbbfdb6441b33fb72609eaefc0



--------------------------------

[ Upstream commit cfcdb5ba ]

The maximum allowed height of an inode's metadata tree depends on the
filesystem block size; it is lower for bigger-block filesystems.  When
reading in an inode, make sure that the height doesn't exceed the
maximum allowed height.

Arrays like sd_heightsize are sized to be big enough for any filesystem
block size; they will often be slightly bigger than what's needed for a
specific filesystem.

Reported-by:  <syzbot+45d4691b1ed3c48eba05@syzkaller.appspotmail.com>
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Signed-off-by: sanglipeng <sanglipeng1@jd.com>