From: Jeff Layton <jlayton@redhat.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] fuse: set mapping error in writepage_locked when it fails
Date: Tue, 30 May 2017 06:26:39 -0400 [thread overview]
Message-ID: <1496139999.2811.1.camel@redhat.com> (raw)
In-Reply-To: <CAJfpegtu7ZrX+-0v2aU-NFwBhuvtNkce9g47ZEdTUP3RDDWCbQ@mail.gmail.com>
On Mon, 2017-05-29 at 15:04 +0200, Miklos Szeredi wrote:
> On Thu, May 25, 2017 at 12:57 PM, Jeff Layton <jlayton@redhat.com> wrote:
> > This ensures that we see errors on fsync when writeback fails.
> >
> > Signed-off-by: Jeff Layton <jlayton@redhat.com>
> > Reviewed-by: Christoph Hellwig <hch@lst.de>
> > Reviewed-by: Jan Kara <jack@suse.cz>
>
> This is currently the only fuse patch for 4.12. Do you plan to send a
> pull to Linus with related things? If so then please feel free to
> take this and add my
>
> Acked-by: Miklos Szeredi <mszeredi@redhat.com>
>
No, I wasn't planning to send a PR to Linus.
I was really expecting these to go into v4.13 anyway (and maybe linux-
next for now). I don't think it'll hurt to merge them into v4.12 though
if you end up with other FUSE patches for v4.12 and want to merge it
earlier.
> > ---
> > fs/fuse/file.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/fs/fuse/file.c b/fs/fuse/file.c
> > index 3ee4fdc3da9e..18518298d109 100644
> > --- a/fs/fuse/file.c
> > +++ b/fs/fuse/file.c
> > @@ -1669,6 +1669,7 @@ static int fuse_writepage_locked(struct page *page)
> > err_free:
> > fuse_request_free(req);
> > err:
> > + mapping_set_error(page->mapping, error);
> > end_page_writeback(page);
> > return error;
> > }
> > --
> > 2.9.4
> >
Thanks,
--
Jeff Layton <jlayton@redhat.com>
prev parent reply other threads:[~2017-05-30 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 10:57 [PATCH] fuse: set mapping error in writepage_locked when it fails Jeff Layton
2017-05-29 13:04 ` Miklos Szeredi
2017-05-30 10:26 ` Jeff Layton [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=1496139999.2811.1.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--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 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.