linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Qian Cai <cai@lca.pw>, Hugh Dickins <hughd@google.com>,
	Matthew Wilcox <willy@infradead.org>,
	"Kirill A . Shutemov" <kirill@shutemov.name>,
	Linux-MM <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Amir Goldstein <amir73il@gmail.com>
Subject: Re: Possible deadlock in fuse write path (Was: Re: [PATCH 0/4] Some more lock_page work..)
Date: Tue, 9 Feb 2021 14:09:19 -0500	[thread overview]
Message-ID: <20210209190919.GE3171@redhat.com> (raw)
In-Reply-To: <20210209100115.GB1208880@miu.piliscsaba.redhat.com>

On Tue, Feb 09, 2021 at 11:01:15AM +0100, Miklos Szeredi wrote:
> Hi Vivek,
> 
> Here's an updated patch with a header comment containing all the gory details.
> It's basically your patch, but it's missing your S-o-b.  If you are fine with
> it, can you please provide one?
> 
> The only change I made was to clear PG_uptodate on write error, otherwise I
> think the patch is fine.

Hi Miklos,

In general I am fine with the patch. I am still little concerned with
how to handle error scenario and how to handle it best. Whether to
clear Pageuptodate on error or leave it alone. Leaving it alone will
more like be writeback failure scenario where many filesystems don't
set dirty flag on page again if writeback fails. 

Can't decide whether to leave it alone is better or not. So for now, I
will just go along with clearing PageUptodate on error.

Can you please also put Link to this mail thread in the commit id. There
are quite a few good details in this mail thread. Will be good to be
able to track it back from commit.

Link: https://lore.kernel.org/linux-fsdevel/4794a3fa3742a5e84fb0f934944204b55730829b.camel@lca.pw/

With that.

Signed-off-by: Vivek Goyal <vgoyal@redhat.com>


> 
> Splitting the request might cause a performance regression in some cases (lots
> of unaligned writes that spill over a page boundary) but I don't have a better
> idea at this moment.
> 
> Thanks,
> Miklos
> ----
> 
> Date: Wed, 21 Oct 2020 16:12:49 -0400
> From: Vivek Goyal <vgoyal@redhat.com>
> Subject: fuse: fix write deadlock
> 
> There are two modes for write(2) and friends in fuse:
> 
> a) write through (update page cache, send sync WRITE request to userspace)
> 
> b) buffered write (update page cache, async writeout later)
> 
> The write through method kept all the page cache pages locked that were
> used for the request.  Keeping more than one page locked is deadlock prone
> and Qian Cai demonstrated this with trinity fuzzing.
> 
> The reason for keeping the pages locked is that concurrent mapped reads
> shouldn't try to pull possibly stale data into the page cache.
> 
> For full page writes, the easy way to fix this is to make the cached page
> be the authoritative source by marking the page PG_uptodate immediately.
> After this the page can be safely unlocked, since mapped/cached reads will
> take the written data from the cache.
> 
> Concurrent mapped writes will now cause data in the original WRITE request
> to be updated; this however doesn't cause any data inconsistency and this
> scenario should be exceedingly rare anyway.
> 
> If the WRITE request returns with an error in the above case, currently the
> page is not marked uptodate; this means that a concurrent read will always
> read consistent data.  After this patch the page is uptodate between
> writing to the cache and receiving the error: there's window where a cached
> read will read the wrong data.  While theoretically this could be a
> regression, it is unlikely to be one in practice, since this is normal for
> buffered writes.
> 
> In case of a partial page write to an already uptodate page the locking is
> also unnecessary, with the above caveats.
> 
> Partial write of a not uptodate page still needs to be handled.  One way
> would be to read the complete page before doing the write.  This is not
> possible, since it might break filesystems that don't expect any READ
> requests when the file was opened O_WRONLY.
> 
> The other solution is to serialize the synchronous write with reads from
> the partial pages.  The easiest way to do this is to keep the partial pages
> locked.  The problem is that a write() may involve two such pages (one head
> and one tail).  This patch fixes it by only locking the partial tail page.
> If there's a partial head page as well, then split that off as a separate
> WRITE request.
> 
> Reported-by: Qian Cai <cai@lca.pw>
> Fixes: ea9b9907b82a ("fuse: implement perform_write")
> Cc: <stable@vger.kernel.org> # v2.6.26
> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
> ---
>  fs/fuse/file.c   |   25 +++++++++++++++----------
>  fs/fuse/fuse_i.h |    1 +
>  2 files changed, 16 insertions(+), 10 deletions(-)
> 
> --- a/fs/fuse/file.c
> +++ b/fs/fuse/file.c
> @@ -1117,17 +1117,12 @@ static ssize_t fuse_send_write_pages(str
>  	count = ia->write.out.size;
>  	for (i = 0; i < ap->num_pages; i++) {
>  		struct page *page = ap->pages[i];
> +		bool page_locked = ap->page_locked && (i == ap->num_pages - 1);
>  
> -		if (!err && !offset && count >= PAGE_SIZE)
> -			SetPageUptodate(page);
> -
> -		if (count > PAGE_SIZE - offset)
> -			count -= PAGE_SIZE - offset;
> -		else
> -			count = 0;
> -		offset = 0;
> -
> -		unlock_page(page);
> +		if (err)
> +			ClearPageUptodate(page);
> +		if (page_locked)
> +			unlock_page(page);
>  		put_page(page);
>  	}
>  
> @@ -1191,6 +1186,16 @@ static ssize_t fuse_fill_write_pages(str
>  		if (offset == PAGE_SIZE)
>  			offset = 0;
>  
> +		/* If we copied full page, mark it uptodate */
> +		if (tmp == PAGE_SIZE)
> +			SetPageUptodate(page);
> +
> +		if (PageUptodate(page)) {
> +			unlock_page(page);
> +		} else {
> +			ap->page_locked = true;
> +			break;
> +		}
>  		if (!fc->big_writes)
>  			break;
>  	} while (iov_iter_count(ii) && count < fc->max_write &&
> --- a/fs/fuse/fuse_i.h
> +++ b/fs/fuse/fuse_i.h
> @@ -277,6 +277,7 @@ struct fuse_args_pages {
>  	struct page **pages;
>  	struct fuse_page_desc *descs;
>  	unsigned int num_pages;
> +	bool page_locked;
>  };
>  
>  #define FUSE_ARGS(args) struct fuse_args args = {}
> 



  reply	other threads:[~2021-02-09 19:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 19:59 [PATCH 0/4] Some more lock_page work Linus Torvalds
2020-10-13 20:03 ` Linus Torvalds
2020-10-14 13:05   ` Kirill A. Shutemov
2020-10-14 16:53     ` Linus Torvalds
2020-10-14 18:15       ` Matthew Wilcox
2020-10-15 10:41         ` Kirill A. Shutemov
2020-10-15  9:43       ` Kirill A. Shutemov
2020-10-15 16:44         ` Linus Torvalds
2020-10-14  5:50 ` Hugh Dickins
     [not found] ` <4794a3fa3742a5e84fb0f934944204b55730829b.camel@lca.pw>
2020-10-15  2:44   ` Linus Torvalds
2020-10-15 15:16     ` Possible deadlock in fuse write path (Was: Re: [PATCH 0/4] Some more lock_page work..) Vivek Goyal
2020-10-15 19:55       ` Vivek Goyal
2020-10-15 21:21         ` Linus Torvalds
2020-10-16 10:02           ` Miklos Szeredi
2020-10-16 12:27             ` Matthew Wilcox
2020-10-20 20:42             ` Vivek Goyal
2020-10-21  7:40               ` Miklos Szeredi
2020-10-21 20:12                 ` Vivek Goyal
2020-10-28 20:29                   ` Miklos Szeredi
2021-02-09 10:01                     ` Miklos Szeredi
2021-02-09 19:09                       ` Vivek Goyal [this message]
2020-10-16 18:19           ` Vivek Goyal
2020-10-16 18:24             ` Linus Torvalds
2020-10-16 18:24               ` Linus Torvalds
2020-10-16 23:03             ` Dave Chinner

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=20210209190919.GE3171@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=amir73il@gmail.com \
    --cc=cai@lca.pw \
    --cc=hughd@google.com \
    --cc=kirill@shutemov.name \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=miklos@szeredi.hu \
    --cc=torvalds@linux-foundation.org \
    --cc=willy@infradead.org \
    --subject='Re: Possible deadlock in fuse write path (Was: Re: [PATCH 0/4] Some more lock_page work..)' \
    /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

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).