From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Stefan Walter <stefan.walter@inf.ethz.ch>
Subject: Re: [NFS] rpc.mountd crashes when extensively using netgroups
Date: Thu, 2 Aug 2007 12:05:36 -0400 [thread overview]
Message-ID: <20070802160536.GF21282@fieldses.org> (raw)
In-Reply-To: <20070802113255.d686894c.jlayton@redhat.com>
On Thu, Aug 02, 2007 at 11:32:55AM -0400, Jeff Layton wrote:
> On Tue, 31 Jul 2007 10:48:24 -0400
> "J. Bruce Fields" <bfields@fieldses.org> wrote:
> > That's an interesting problem. Thanks for the report!
> >
> > I don't believe that long comma-delimited string actually has any
> > meaning to the kernel--as far as the kernel is concerned, it's just an
> > opaque object that will be passed back to mountd later (along with a
> > path name) to get export options.
> >
> > So I suppose that string could be replaced by a hash, or maybe even just
> > by the ip address of the particular host--the disadvantage to the latter
> > being that it would require the kernel to keep a separate export for
> > each client address.
>
> I started having a look at this today. The original patches that I
> proposed to clean up the rmtab a few months ago also eliminated this
> comma-delimited string. Neil had valid objections to it at the time,
> but if we switched to using the IP address as a cache key like Bruce
> describes then doing that becomes more reasonable.
>
> The only downside I see is the one Bruce points out -- the size of
> the kernel export cache would increase. I don't have a feel for whether
> this is a show stopper, however.
Yeah, there might be some risk of solving that problem at the expense of
people with tons of clients all matching *.example.com. The actual
export objects are actually pretty small--68 bytes, last I checked?
You'd also need two upcalls to mountd per client (for ip address and
export, as opposed to just ip address). I don't know what other costs
there might be.
What about the idea of hashing the comma-delimited list and passing
that? You'd want hash large enough to be collision-free--might as well
use some cryptographic hash, I guess, though it may be mild overkill.
Is there any reason why that wouldn't work?
Could you remind me what problems you were trying to fix with your rmtab
cleanup?
--b.
next prev parent reply other threads:[~2007-08-02 16:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 12:55 rpc.mountd crashes when extensively using netgroups Stefan Walter
2007-07-31 13:59 ` Steve Dickson
2007-08-02 9:04 ` Stefan Walter
2007-08-03 2:40 ` Satyam Sharma
2007-08-03 14:51 ` Steve Dickson
2007-07-31 14:48 ` J. Bruce Fields
2007-08-02 15:32 ` [NFS] " Jeff Layton
2007-08-02 16:05 ` J. Bruce Fields [this message]
2007-08-02 16:28 ` Jeff Layton
2007-08-03 3:01 ` Neil Brown
2007-08-03 7:57 ` Stefan Walter
2007-08-03 16:07 ` 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=20070802160536.GF21282@fieldses.org \
--to=bfields@fieldses.org \
--cc=jlayton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=stefan.walter@inf.ethz.ch \
/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