From: Thomas Schlichter <schlicht@uni-mannheim.de>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Oleg Drokin <green@namesys.com>,
linux-kernel@vger.kernel.org, Bill Huey <billh@gnuppy.monkey.org>
Subject: Re: NFS/ReiserFS problems 2.5.64-mbj1
Date: Sun, 30 Mar 2003 21:52:06 +0200 [thread overview]
Message-ID: <200303302152.08197.schlicht@uni-mannheim.de> (raw)
In-Reply-To: <16005.11608.478233.424677@notabene.cse.unsw.edu.au>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 766 bytes --]
On March 29, Neil Brown wrote:
> One possibility is that you are using the new nfs-utils 1.0.3, but you
> reported the bug before I announced it (though it was in CVS and on
> kernel.org by then so maybe...)!
You are right, I am using the nfs-utils 1.0.3 as I downloaded them as soon as
I saw them on kernel.org... ;-)
> The new code uses a different path to export filesystems which didn't
> include the setting of find_exported_dentry.
> The following patch should fix that.
Thank you!
I'll try it tonight and write you my results...
> If you aren't using 1.0.3, then I am at a loss. A filesystem can only
> be exported via call to exp_export, and that does set
> sb->s_export_op->find_exported_dentry
>
> NeilBrown
Thomas Schlichter
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-03-30 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 9:22 NFS/ReiserFS problems 2.5.64-mbj1 Bill Huey
2003-03-27 17:07 ` Oleg Drokin
2003-03-28 9:12 ` Thomas Schlichter
2003-03-28 10:57 ` Thomas Schlichter
2003-03-28 11:45 ` Oleg Drokin
2003-03-29 5:21 ` Neil Brown
2003-03-30 19:52 ` Thomas Schlichter [this message]
2003-03-31 9:12 ` Thomas Schlichter
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=200303302152.08197.schlicht@uni-mannheim.de \
--to=schlicht@uni-mannheim.de \
--cc=billh@gnuppy.monkey.org \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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