From: Ian Kent <raven@themaw.net>
To: Dave Hansen <hansendc@us.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
haveblue@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: Re: Read-only bind mount patches
Date: Tue, 15 May 2007 00:29:59 +0800 [thread overview]
Message-ID: <1179160199.3811.88.camel@raven.themaw.net> (raw)
In-Reply-To: <1179158480.366.8.camel@localhost.localdomain>
On Mon, 2007-05-14 at 09:01 -0700, Dave Hansen wrote:
> On Mon, 2007-05-14 at 23:55 +0800, Ian Kent wrote:
> >
> > Anything I can do to help?
> > If so maybe we could reduce the time to posting a bit.
>
> Probably nothing to actually speed up the development, but I'd really
> appreciate some testing once I do post them. How about I send you an
> advance copy, or cc you on the RFC?
Sure.
My personal test environment is limited.
I can test them with the autofs Connectathon suite and do sanity
checking and the like.
In my other life I can spin a RHEL5 kernel in a private branch and get
that to customers that are complaining, hopefully they will be willing
to test this stuff and persevere with any needed debugging (ya right).
I'm happy to screen reports before passing them on and hopefully provide
you with sensible feedback. But it would be best if we could at least
get this into the mm kernel. That should get them a fair bit of
exposure.
The other question for me is I don't know yet if this will resolve the
problem that lead me to chase this. That's the problem where all NFS
client mounts to the same exported filesystem always use the mount
options of the first mount.
Are you sure I can't help with development, even just re-spinning them
against the current kernel may help (of course you would know best).
Having read the patch set in the archives I see that I'm familiar with
the code in most of the areas of the VFS they touch (but maybe not to
the depth that I would like).
Ian
prev parent reply other threads:[~2007-05-14 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 13:22 Ian Kent
2007-05-14 15:10 ` Dave Hansen
2007-05-14 15:55 ` Ian Kent
2007-05-14 16:01 ` Dave Hansen
2007-05-14 16:29 ` Ian Kent [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=1179160199.3811.88.camel@raven.themaw.net \
--to=raven@themaw.net \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=hansendc@us.ibm.com \
--cc=haveblue@linux.vnet.ibm.com \
--cc=hch@infradead.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®