From: Oleg Drokin <green@namesys.com>
To: Thomas Schlichter <schlicht@uni-mannheim.de>
Cc: linux-kernel@vger.kernel.org, neilb@cse.unsw.edu.au,
Bill Huey <billh@gnuppy.monkey.org>
Subject: Re: NFS/ReiserFS problems 2.5.64-mbj1
Date: Fri, 28 Mar 2003 14:45:12 +0300 [thread overview]
Message-ID: <20030328144512.A13144@namesys.com> (raw)
In-Reply-To: <200303281157.51743.schlicht@uni-mannheim.de>
Hello!
On Fri, Mar 28, 2003 at 11:57:42AM +0100, Thomas Schlichter wrote:
> On Mar 27, 2003 18:07, Oleg Drokin wrote:
> > sb->s_export_op->find_exported_dentry is NULL
> > in reiserfs_decode_fh, well. In fact we never set this field at all.
> > What is supposed to be there, anyway?
> > I guess following patch should fix the problem.
> Yes, it did fix the problem, but now I was not allowed anymore to compile NFS
> as a module as I need reiserfs to be in the kernel... :-(
Well, in fact this not real fix as I see it, it is just a cover for different bug somewhere else.
> > In fact I guess somebody should put find_exported_dentry() declaration to
> > include/linux/fs.h or something like that.
> > Also absolutely the same problem must exist if you try to export fat
> filesystem.
> That is true, too. I saw the Oops with a VFAT partition, too
> I just wonder why the code in fs/nfsd/export.c lines 684-687 does not work.
Well, I run the thing in the debugger with current bk snapshot and everything worked.
> This code should set the find_exported_dentry field correctly. But I do not
> know when this function (exp_export()) is called...
it is called when you mount remote fs, as my debugging session shows.
So I guess problem was already fixed somewhere else.
Bye,
Oleg
next prev parent reply other threads:[~2003-03-28 11:34 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 [this message]
2003-03-29 5:21 ` Neil Brown
2003-03-30 19:52 ` Thomas Schlichter
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=20030328144512.A13144@namesys.com \
--to=green@namesys.com \
--cc=billh@gnuppy.monkey.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=schlicht@uni-mannheim.de \
/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