All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 0/3] nfsd: add a usermodehelper upcall for client id tracking
Date: Fri, 5 Oct 2012 10:34:47 -0400	[thread overview]
Message-ID: <20121005143447.GA15134@fieldses.org> (raw)
In-Reply-To: <1349268031-16498-1-git-send-email-jlayton@redhat.com>

On Wed, Oct 03, 2012 at 08:40:28AM -0400, Jeff Layton wrote:
> This is a respin of the set with the same title that I sent on Monday
> (Oct 1st). This one has a few bugfixes, and adds some code to allow the
> upcall program to convert from the legacy database to the new one. I'll
> also be posting a respin of the companion nfs-utils set too.
> 
> The idea here is to allow a one-way conversion from the legacy clientid
> tracking code to the new one, which should allow for seamless kernel and
> nfs-utils upgrades.
> 
> In order to handle that, this set also changes the heuristic that the
> kernel uses to decide what client tracker to use. We now must now try
> the usermodehelper upcall first and only fall back to other schemes if
> its initialization fails.
> 
> Note that I'm not 100% sold on the idea to convert from the legacy db
> format. It's doable but somewhat "fiddly" to handle. There are probably
> corner cases where it will fall down, so it may be best not to even try
> to do that. I won't be offended if you decide not to take the last
> patch.
> 
> Comments? Discuss!

So that's take 3 at reboot recovery.  Take 1 is what people actually use
(despite it being ugly), take 2 nobody's using yet--so it could probably
be ripped out fairly quickly.

I don't see anything objectionable on a quick skim.

I'd rather wait a little longer and consider it for the next merge
window.

--b.

      parent reply	other threads:[~2012-10-05 14:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03 12:40 [PATCH v2 0/3] nfsd: add a usermodehelper upcall for client id tracking Jeff Layton
2012-10-03 12:40 ` [PATCH v2 1/3] nfsd: add a usermodehelper upcall for NFSv4 client ID tracking Jeff Layton
2012-10-05 14:36   ` J. Bruce Fields
2012-10-05 14:47     ` Jeff Layton
2012-10-03 12:40 ` [PATCH v2 2/3] nfsd: change heuristic for selecting the client_tracking_ops Jeff Layton
2012-10-03 12:40 ` [PATCH v2 3/3] nfsd: pass info about the legacy recoverydir in environment variables Jeff Layton
2012-10-05 14:34 ` J. Bruce Fields [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=20121005143447.GA15134@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=jlayton@redhat.com \
    --cc=linux-nfs@vger.kernel.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 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.