From: Jan Kara <jack@suse.cz>
To: Abhijith Das <adas@redhat.com>
Cc: Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Bob Peterson <rpeterso@redhat.com>
Subject: Re: [RFC v2 PATCH] fs: __generic_file_splice_read retry lookup on AOP_TRUNCATED_PAGE
Date: Wed, 16 Dec 2015 17:47:45 +0100 [thread overview]
Message-ID: <20151216164745.GA29214@quack.suse.cz> (raw)
In-Reply-To: <1471602670.34527814.1450281325831.JavaMail.zimbra@redhat.com>
On Wed 16-12-15 10:55:25, Abhijith Das wrote:
> > > @@ -439,14 +441,13 @@ __generic_file_splice_read(struct file *in, loff_t
> > > *ppos,
> > > error = mapping->a_ops->readpage(in, page);
> > > if (unlikely(error)) {
> > > /*
> > > - * We really should re-lookup the page here,
> > > - * but it complicates things a lot. Instead
> > > - * lets just do what we already stored, and
> > > - * we'll get it the next time we are called.
> > > + * Re-lookup the page
> > > */
> > > - if (error == AOP_TRUNCATED_PAGE)
> > > + if (error == AOP_TRUNCATED_PAGE) {
> > > error = 0;
> > > -
> > > + if (retries++ < 3)
> > > + goto retry_lookup;
> > > + }
> >
> > I don't like this retry-three-times loop. That is still leaving the
> > possibility of 0 return just much less likely (so it will lead to even
> > weirder and harded to debug failures). IMO we should just terminate the
> > loop like we did previously if spd.nr_pages > 0 and we retry indefinitely
> > if it is the first page that failed to read.
>
> The 3-retry loop was the thing I was unsure about too. With regards to the
> indefinite retry, I was wondering if there's some corner case where we might
> get into an infinite retry loop...
Well you have two options:
1) Return incorrect value from splice_read()
2) Retry indefinitely
Option two looks better to me. Also do_generic_file_read() behaves the same
way so mirroring the behavior in __generic_file_splice_read() makes sense.
> If we're doing the retry for the first page, why not for other pages too?
> Is it because we'd potentially be increasing the odds for an infinite
> loop and/or affecting performance by doing more lookups?
Yes, that was my thought. But seeing now that do_generic_file_read()
actually retries indefinitely for every page, I'd just do the same in
__generic_file_splice_read().
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2015-12-16 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 15:43 [RFC v2 PATCH] fs: __generic_file_splice_read retry lookup on AOP_TRUNCATED_PAGE Abhi Das
2015-12-16 15:34 ` Jan Kara
2015-12-16 15:55 ` Abhijith Das
2015-12-16 16:47 ` Jan Kara [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=20151216164745.GA29214@quack.suse.cz \
--to=jack@suse.cz \
--cc=adas@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpeterso@redhat.com \
/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