From: Andreas Gruenbacher <agruenba@redhat.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: cluster-devel <cluster-devel@redhat.com>,
"Christoph Hellwig" <hch@lst.de>,
"Bob Peterson" <rpeterso@redhat.com>, "Jan Kara" <jack@suse.cz>,
"Dave Chinner" <david@fromorbit.com>,
"Ross Lagerwall" <ross.lagerwall@citrix.com>,
"Mark Syms" <Mark.Syms@citrix.com>,
"Edwin Török" <edvin.torok@citrix.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [PATCH v2 1/2] iomap: Add a page_prepare callback
Date: Thu, 25 Apr 2019 17:52:19 +0200 [thread overview]
Message-ID: <CAHc6FU6hNiQhzQq3+Z_efPpon6LfB_8i+OQqOUVQg7uZ-wPJRA@mail.gmail.com> (raw)
In-Reply-To: <20190425152940.GJ19031@bombadil.infradead.org>
On Thu, 25 Apr 2019 at 17:29, Matthew Wilcox <willy@infradead.org> wrote:
>
> On Thu, Apr 25, 2019 at 05:26:30PM +0200, Andreas Gruenbacher wrote:
>
> This seems to be corrupted; there's no declaration of a page_ops in
> iomap_write_begin ... unless you're basing on a patch I don't have?
Oops, this has slipped into the 2nd patch, sorry.
> > diff --git a/fs/iomap.c b/fs/iomap.c
> > index 97cb9d486a7d..967c985c5310 100644
> > --- a/fs/iomap.c
> > +++ b/fs/iomap.c
> > @@ -674,9 +674,17 @@ iomap_write_begin(struct inode *inode, loff_t pos, unsigned len, unsigned flags,
> > if (fatal_signal_pending(current))
> > return -EINTR;
> >
> > + if (page_ops) {
> > + status = page_ops->page_prepare(inode, pos, len, iomap);
> > + if (status)
> > + return status;
> > + }
> > +
> > page = grab_cache_page_write_begin(inode->i_mapping, index, flags);
> > - if (!page)
> > - return -ENOMEM;
> > + if (!page) {
> > + status = -ENOMEM;
> > + goto no_page;
> > + }
> >
> > if (iomap->type == IOMAP_INLINE)
> > iomap_read_inline_data(inode, page, iomap);
Andreas
prev parent reply other threads:[~2019-04-25 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 15:26 Andreas Gruenbacher
2019-04-25 15:26 ` [PATCH v2 2/2] gfs2: Fix iomap write page reclaim deadlock Andreas Gruenbacher
2019-04-25 15:29 ` [PATCH v2 1/2] iomap: Add a page_prepare callback Matthew Wilcox
2019-04-25 15:52 ` Andreas Gruenbacher [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=CAHc6FU6hNiQhzQq3+Z_efPpon6LfB_8i+OQqOUVQg7uZ-wPJRA@mail.gmail.com \
--to=agruenba@redhat.com \
--cc=Mark.Syms@citrix.com \
--cc=cluster-devel@redhat.com \
--cc=david@fromorbit.com \
--cc=edvin.torok@citrix.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ross.lagerwall@citrix.com \
--cc=rpeterso@redhat.com \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox