From: Al Viro <viro@zeniv.linux.org.uk>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, Daeho Jeong <daeho43@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] vfs: don't unnecessarily clone write access for writable fds
Date: Mon, 4 Jan 2021 19:08:32 +0000 [thread overview]
Message-ID: <20210104190832.GL3579531@ZenIV.linux.org.uk> (raw)
In-Reply-To: <X/Nkk4rlS43W90TV@sol.localdomain>
On Mon, Jan 04, 2021 at 10:55:15AM -0800, Eric Biggers wrote:
> On Tue, Sep 22, 2020 at 09:44:18AM -0700, Eric Biggers wrote:
> > From: Eric Biggers <ebiggers@google.com>
> >
> > 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>
> > ---
> >
> > v3: added note to porting file.
> > v2: keep the check for emergency r/o remounts.
> >
> > Documentation/filesystems/porting.rst | 7 ++++
> > fs/namespace.c | 53 ++++++++++-----------------
> > include/linux/mount.h | 1 -
> > 3 files changed, 27 insertions(+), 34 deletions(-)
>
> Ping.
Applied.
prev parent reply other threads:[~2021-01-04 19:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 16:44 [PATCH v3] vfs: don't unnecessarily clone write access for writable fds Eric Biggers
2021-01-04 18:55 ` Eric Biggers
2021-01-04 19:08 ` Al Viro [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210104190832.GL3579531@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=daeho43@gmail.com \
--cc=ebiggers@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.