fs/minix: set s_maxbytes correctly
authorEric Biggers <ebiggers@google.com>
Wed, 12 Aug 2020 01:35:33 +0000 (18:35 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Wed, 12 Aug 2020 17:58:00 +0000 (10:58 -0700)
commit32ac86efff91a3e4ef8c3d1cadd4559e23c8e73a
tree423bd6c227851776d467bf60624581a19ea30522
parent270ef41094e9fa95273f288d7d785313ceab2ff3
fs/minix: set s_maxbytes correctly

The minix filesystem leaves super_block::s_maxbytes at MAX_NON_LFS rather
than setting it to the actual filesystem-specific limit.  This is broken
because it means userspace doesn't see the standard behavior like getting
EFBIG and SIGXFSZ when exceeding the maximum file size.

Fix this by setting s_maxbytes correctly.

Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Qiujun Huang <anenbupt@gmail.com>
Link: http://lkml.kernel.org/r/20200628060846.682158-5-ebiggers@kernel.org
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
fs/minix/inode.c
fs/minix/itree_v1.c
fs/minix/itree_v2.c
fs/minix/minix.h