Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Neil Brown <neilb@suse.com>
Cc: Olaf Kirch <okir@suse.de>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH/RFC] sunrpc/cache: make cache flushing more reliable.
Date: Thu, 15 Oct 2015 09:50:39 -0400	[thread overview]
Message-ID: <20151015135039.GB18976@fieldses.org> (raw)
In-Reply-To: <87a8rkws7g.fsf@notabene.neil.brown.name>

On Thu, Oct 15, 2015 at 05:39:47PM +1100, Neil Brown wrote:
> 
> Sorry.. I didn't refresh before posting....
> 
> > @@ -487,10 +496,13 @@ EXPORT_SYMBOL_GPL(cache_flush);
> >  
> >  void cache_purge(struct cache_detail *detail)
> >  {
> > -	detail->flush_time = LONG_MAX;
> > +	time_t now = seconds_since_boot();
> > +	if (detail->flush_time >= now)
> > +		now = detail->flush_time + 1;
> > +	/* 'now' is the maximum value any 'last_refresh' can have */
> > +	detail->flush_time = now + 1;
> 
> This should not have the '+ 1'.
> 
> >  	detail->nextcheck = seconds_since_boot();
> >  	cache_flush();
> > -	detail->flush_time = 1;
> >  }
> >  EXPORT_SYMBOL_GPL(cache_purge);
> >  
> > @@ -1447,8 +1460,22 @@ static ssize_t write_flush(struct file *file, const char __user *buf,
> >  		return -EINVAL;
> >  
> >  	bp = tbuf;
> > -	cd->flush_time = get_expiry(&bp);
> > -	cd->nextcheck = seconds_since_boot();
> > +	then = get_expiry(&bp);
> > +	now = seconds_since_boot();
> > +	cd->nextcheck = now;
> > +	/* Can only set flush_time to 1 second beyond "now", or
> > +	 * possibly 1 second beyond flushtime.  This is because
> > +	 * flush_time never goes backwards so it mustn't get too far
> > +	 * ahead of time.
> > +	 */
> > +	if (then >= now) {
> > +		/* Want to flush everything, so behave like cache_purge() */
> > +		if (cd->flush_time >= now)
> > +			now = cd->flush_time + 1;
> > +		then = now + 1;
> 
> Nor should.
> 
> I'll resend it people are otherwise happy.

I'm otherwise happy!  Looks like a reasonable approach.

(The one thing I wonder is whether it would be clearer to outright fail
writes that attempt to create already-expired cache entries.

But I think that's an unimportant corner case really.  And if there are
existing cases where that's happening then perhaps it's less disruptive
just to let them expire a second later rathern than to introduce a new
error.)

--b.

  reply	other threads:[~2015-10-15 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15  6:31 [PATCH/RFC] sunrpc/cache: make cache flushing more reliable Neil Brown
2015-10-15  6:39 ` Neil Brown
2015-10-15 13:50   ` J. Bruce Fields [this message]
2015-10-15 21:57     ` Neil Brown
2015-10-15 21:59     ` [PATCH v2] " Neil Brown
2015-10-22 19:14       ` J. Bruce Fields

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=20151015135039.GB18976@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.com \
    --cc=okir@suse.de \
    /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