vfs: don't unnecessarily clone write access for writable fds
authorEric Biggers <ebiggers@google.com>
Tue, 22 Sep 2020 16:44:18 +0000 (09:44 -0700)
committerAl Viro <viro@zeniv.linux.org.uk>
Mon, 4 Jan 2021 19:02:08 +0000 (14:02 -0500)
commit14e43bf435612639cab01541fce7cc41bf7e370b
treed0a418ace1f97fbdc4ad4fcf88ce5119237bccdd
parent5c8fe583cce542aa0b84adc939ce85293de36e5e
vfs: don't unnecessarily clone write access for writable fds

There's no need for mnt_want_write_file() to increment mnt_writers when
the file is already open for writing, provided that
mnt_drop_write_file() is changed to conditionally decrement it.

We seem to have ended up in the current situation because
mnt_want_write_file() used to be paired with mnt_drop_write(), due to
mnt_drop_write_file() not having been added yet.  So originally
mnt_want_write_file() had to always increment mnt_writers.

But later mnt_drop_write_file() was added, and all callers of
mnt_want_write_file() were paired with it.  This makes the compatibility
between mnt_want_write_file() and mnt_drop_write() no longer necessary.

Therefore, make __mnt_want_write_file() and __mnt_drop_write_file() skip
incrementing mnt_writers on files already open for writing.  This
removes the only caller of mnt_clone_write(), so remove that too.

Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Documentation/filesystems/porting.rst
fs/namespace.c
include/linux/mount.h