From: Amir Goldstein <amir73il@gmail.com>
To: Bernd Schubert <bschubert@ddn.com>
Cc: linux-fsdevel@vger.kernel.org, bernd.schubert@fastmail.fm,
miklos@szeredi.hu, dsingh@ddn.com
Subject: Re: [PATCH 2/4] fuse: Create helper function if DIO write needs exclusive lock
Date: Sun, 24 Dec 2023 13:14:44 +0200 [thread overview]
Message-ID: <CAOQ4uxgxG4FinVmPoQmbmcFoioOetrKSD2ZkGKykyiaJQqoT3g@mail.gmail.com> (raw)
In-Reply-To: <20231224104914.49316-3-bschubert@ddn.com>
On Sun, Dec 24, 2023 at 12:49 PM Bernd Schubert <bschubert@ddn.com> wrote:
>
> This makes the code a bit easier to read and allows to more
> easily add more conditions when an exclusive lock is needed.
>
> Signed-off-by: Bernd Schubert <bschubert@ddn.com>
Reviewed-by: Amir Goldstein <amir73il@gmail.com>
> ---
> fs/fuse/file.c | 64 +++++++++++++++++++++++++++++++++++---------------
> 1 file changed, 45 insertions(+), 19 deletions(-)
>
> diff --git a/fs/fuse/file.c b/fs/fuse/file.c
> index 174aa16407c4b..546254aaab19f 100644
> --- a/fs/fuse/file.c
> +++ b/fs/fuse/file.c
> @@ -1298,6 +1298,45 @@ static ssize_t fuse_perform_write(struct kiocb *iocb, struct iov_iter *ii)
> return res;
> }
>
> +static bool fuse_io_past_eof(struct kiocb *iocb, struct iov_iter *iter)
> +{
> + struct inode *inode = file_inode(iocb->ki_filp);
> +
> + return iocb->ki_pos + iov_iter_count(iter) > i_size_read(inode);
> +}
> +
> +/*
> + * @return true if an exclusive lock for direct IO writes is needed
> + */
> +static bool fuse_dio_wr_exclusive_lock(struct kiocb *iocb, struct iov_iter *from)
> +{
> + struct file *file = iocb->ki_filp;
> + struct fuse_file *ff = file->private_data;
> + struct inode *inode = file_inode(iocb->ki_filp);
> +
> + /* server side has to advise that it supports parallel dio writes */
> + if (!(ff->open_flags & FOPEN_PARALLEL_DIRECT_WRITES))
> + return true;
> +
> + /* append will need to know the eventual eof - always needs an
> + * exclusive lock
> + */
> + if (iocb->ki_flags & IOCB_APPEND)
> + return true;
> +
> + /* combination opf page access and direct-io difficult, shared
> + * locks actually introduce a conflict.
> + */
> + if (get_fuse_conn(inode)->direct_io_allow_mmap)
> + return true;
> +
> + /* parallel dio beyond eof is at least for now not supported */
> + if (fuse_io_past_eof(iocb, from))
> + return true;
> +
> + return false;
> +}
> +
> static ssize_t fuse_cache_write_iter(struct kiocb *iocb, struct iov_iter *from)
> {
> struct file *file = iocb->ki_filp;
> @@ -1557,26 +1596,12 @@ static ssize_t fuse_direct_read_iter(struct kiocb *iocb, struct iov_iter *to)
> return res;
> }
>
> -static bool fuse_direct_write_extending_i_size(struct kiocb *iocb,
> - struct iov_iter *iter)
> -{
> - struct inode *inode = file_inode(iocb->ki_filp);
> -
> - return iocb->ki_pos + iov_iter_count(iter) > i_size_read(inode);
> -}
> -
> static ssize_t fuse_direct_write_iter(struct kiocb *iocb, struct iov_iter *from)
> {
> struct inode *inode = file_inode(iocb->ki_filp);
> - struct file *file = iocb->ki_filp;
> - struct fuse_file *ff = file->private_data;
> struct fuse_io_priv io = FUSE_IO_PRIV_SYNC(iocb);
> ssize_t res;
> - bool exclusive_lock =
> - !(ff->open_flags & FOPEN_PARALLEL_DIRECT_WRITES) ||
> - get_fuse_conn(inode)->direct_io_allow_mmap ||
> - iocb->ki_flags & IOCB_APPEND ||
> - fuse_direct_write_extending_i_size(iocb, from);
> + bool exclusive_lock = fuse_dio_wr_exclusive_lock(iocb, from);
>
> /*
> * Take exclusive lock if
> @@ -1590,10 +1615,10 @@ static ssize_t fuse_direct_write_iter(struct kiocb *iocb, struct iov_iter *from)
> else {
> inode_lock_shared(inode);
>
> - /* A race with truncate might have come up as the decision for
> - * the lock type was done without holding the lock, check again.
> + /*
> + * Previous check was without any lock and might have raced.
> */
> - if (fuse_direct_write_extending_i_size(iocb, from)) {
> + if (fuse_dio_wr_exclusive_lock(iocb, from)) {
> inode_unlock_shared(inode);
> inode_lock(inode);
> exclusive_lock = true;
> @@ -2467,7 +2492,8 @@ static int fuse_file_mmap(struct file *file, struct vm_area_struct *vma)
> return fuse_dax_mmap(file, vma);
>
> if (ff->open_flags & FOPEN_DIRECT_IO) {
> - /* Can't provide the coherency needed for MAP_SHARED
> + /*
> + * Can't provide the coherency needed for MAP_SHARED
> * if FUSE_DIRECT_IO_ALLOW_MMAP isn't set.
> */
> if ((vma->vm_flags & VM_MAYSHARE) && !fc->direct_io_allow_mmap)
> --
> 2.40.1
>
next prev parent reply other threads:[~2023-12-24 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-24 10:49 [PATCH 0/4] fuse: inode IO modes and mmap Bernd Schubert
2023-12-24 10:49 ` [PATCH 1/4] fuse: Fix VM_MAYSHARE and direct_io_allow_mmap Bernd Schubert
2023-12-24 10:49 ` [PATCH 2/4] fuse: Create helper function if DIO write needs exclusive lock Bernd Schubert
2023-12-24 11:14 ` Amir Goldstein [this message]
2023-12-24 10:49 ` [PATCH 3/4] fuse: Add fuse_dio_lock/unlock helper functions Bernd Schubert
2023-12-24 11:15 ` Amir Goldstein
2023-12-24 10:49 ` [PATCH 4/4] fuse: introduce inode io modes Bernd Schubert
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=CAOQ4uxgxG4FinVmPoQmbmcFoioOetrKSD2ZkGKykyiaJQqoT3g@mail.gmail.com \
--to=amir73il@gmail.com \
--cc=bernd.schubert@fastmail.fm \
--cc=bschubert@ddn.com \
--cc=dsingh@ddn.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).