From: Jeff Layton <jlayton@poochiereds.net>
To: nfs@lists.sourceforge.net
Cc: Neil Brown <neilb@suse.de>
Subject: Re: [PATCH 0/2] mountd: clean up rmtab handling
Date: Fri, 01 Dec 2006 10:29:14 -0500 [thread overview]
Message-ID: <45704A4A.6000007@poochiereds.net> (raw)
In-Reply-To: <1161781620.7078.50.camel@dantu.rdu.redhat.com>
Jeff Layton wrote:
> We have had a few reports from customers that showmount -a is just plain
> broken.
...
> The following two patches remedy this. They both should only affect the
> case where new_cache is set.
>
> -- Jeff
It's been a little over a month since I originally posted these patches
and haven't received much comment though Neil and I have traded some
emails off list concerning it. I'd like to move the discussion back to
the mailing list to get a wider audience and see if we can come to some
sort of resolution.
When we last communicated, he mentioned a scheme whereby we could
generate the showmount -a info on the fly rather than trying to maintain
the rmtab. That sounds like a good approach, but I don't see how that
can work without some changes in how the caches are managed.
Neil, would it be reasonable to commit these patches now to fix the
immediate problem and then work on the new scheme that synthesizes the
info out of the kernel caches like you proposed?
-- Jeff
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-12-01 15:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 13:07 [PATCH 0/2] mountd: clean up rmtab handling Jeff Layton
2006-12-01 15:29 ` Jeff Layton [this message]
2006-12-04 4:38 ` Neil Brown
2006-12-04 6:33 ` Neil Brown
2006-12-05 2:28 ` Jeff Layton
2006-12-05 2:51 ` Jeff Layton
2006-12-09 12:27 ` Jeff Layton
2006-12-04 15:05 ` Jeff Layton
2006-12-11 1:00 ` Neil Brown
2006-12-11 3:40 ` Jeff Layton
2006-12-12 1:07 ` Neil Brown
2006-12-12 7:52 ` Warren Beldad
2006-12-13 13:17 ` Jeff Layton
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=45704A4A.6000007@poochiereds.net \
--to=jlayton@poochiereds.net \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
/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.