umount(2): move the flag validity checks first
authorAl Viro <viro@zeniv.linux.org.uk>
Mon, 4 Jan 2021 20:25:34 +0000 (15:25 -0500)
committerAl Viro <viro@zeniv.linux.org.uk>
Mon, 4 Jan 2021 20:31:58 +0000 (15:31 -0500)
commita0a6df9afcaf439a6b4c88a3b522e3d05fdef46f
tree7ef2ed36a935d9643b6e6b50988054a603187755
parent5c8fe583cce542aa0b84adc939ce85293de36e5e
umount(2): move the flag validity checks first

Unfortunately, there's userland code that used to rely upon these
checks being done before anything else to check for UMOUNT_NOFOLLOW
support.  That broke in 41525f56e256 ("fs: refactor ksys_umount").
Separate those from the rest of checks and move them to ksys_umount();
unlike everything else in there, this can be sanely done there.

Reported-by: Sargun Dhillon <sargun@sargun.me>
Fixes: 41525f56e256 ("fs: refactor ksys_umount")
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
fs/namespace.c