Andreas Gruenbacher d485903231 gfs2: Fix inode height consistency check
[ Upstream commit cfcdb5bad34f600aed7613c3c1a5e618111f77b7 ]

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>
2023-05-24 17:32:37 +01:00
..
2023-03-10 09:33:25 +01:00
2021-06-29 10:56:51 +02:00
2022-08-06 14:44:49 -07:00
2022-05-09 23:12:33 -04:00
2022-08-03 10:35:43 -07:00
2022-09-11 20:26:06 -07:00
2022-09-11 20:26:06 -07:00
2022-02-02 07:49:59 -07:00
2022-06-28 20:38:15 +02:00