From: "J. Bruce Fields" <bfields@fieldses.org>
To: Simo Sorce <simo@redhat.com>
Cc: "Myklebust, Trond" <Trond.Myklebust@netapp.com>,
Chuck Lever <chuck.lever@oracle.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: synchronous AF_LOCAL connect
Date: Thu, 21 Feb 2013 11:39:52 -0500 [thread overview]
Message-ID: <20130221163952.GD9743@fieldses.org> (raw)
In-Reply-To: <20130221162139.GB9743@fieldses.org>
On Thu, Feb 21, 2013 at 11:21:39AM -0500, J. Bruce Fields wrote:
> On Wed, Feb 20, 2013 at 06:03:37PM -0500, J. Bruce Fields wrote:
> > OK, I've added that check and fixed some other bugs (thanks to Chuck for
> > some help in IRC).
> >
> > I think that gets rpcbind working in containers fine.
> >
> > gss-proxy has one more problem: it needs to do upcalls from nfsd threads
> > which won't have the right filesystem namespace.
> >
> > I get a write from gss-proxy when it starts and can do an initial
> > connect then using its context. But if we disconnect after that I'm
> > stuck.
> >
> > Does it cause any problems if I just set the idle_timeout to 0 for
> > AF_LOCAL?
>
> That gives me the following three patches. They work for me.
>
> Would it make more sense to make the idle timeout configurable? I
> couldn't see why disconnecting idle AF_LOCAL rpcbind connections would
> be particularly important anyway.
Also posted a new version of the gss-proxy series including these
patches.
--b.
next prev parent reply other threads:[~2013-02-21 16:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 22:54 synchronous AF_LOCAL connect J. Bruce Fields
2013-02-20 15:47 ` J. Bruce Fields
2013-02-20 15:56 ` Chuck Lever
2013-02-20 16:03 ` J. Bruce Fields
2013-02-20 16:20 ` Chuck Lever
2013-02-20 16:34 ` J. Bruce Fields
2013-02-20 17:04 ` Chuck Lever
2013-02-20 17:27 ` Myklebust, Trond
2013-02-20 17:32 ` Simo Sorce
2013-02-20 23:03 ` J. Bruce Fields
2013-02-21 16:21 ` J. Bruce Fields
2013-02-21 16:27 ` Chuck Lever
2013-02-21 16:30 ` J. Bruce Fields
2013-02-21 16:39 ` J. Bruce Fields [this message]
2013-02-20 17:39 ` Chuck Lever
2013-02-20 18:02 ` Myklebust, Trond
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=20130221163952.GD9743@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=simo@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 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.