From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Menny Hamburger <menny@exanet.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, linux-kernel@vger.kernel.org
Subject: RE: Getting the nfs_fh of a specific file/dir from the kernel
Date: Tue, 13 Feb 2007 15:13:01 -0800 [thread overview]
Message-ID: <1171408381.6031.1.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <A6FDE6B975803043804A49F12F49028E0F573D@hawk.exanet-il.co.il>
On Sun, 2007-02-11 at 10:06 +0200, Menny Hamburger wrote:
> We implement our own nfsd in user space - so the kernel nfsd (as well
> as the lockd) are disabled.
> We need the handle in order to associate a kernel file handle with our
> own file id.
Filehandles are not part of any API that is exported to userland. There
are many reasons why that would be a bad idea.
Cheers
Trond
> M.
>
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of J. Bruce Fields
> Sent: Thursday, February 08, 2007 10:12 PM
> To: Menny Hamburger
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: Getting the nfs_fh of a specific file/dir from the kernel
>
> On Thu, Feb 08, 2007 at 06:38:48PM +0200, Menny Hamburger wrote:
> > I have a piece of code in my 2.6 kernel that associates an ioctl
> > file_operation to nfs in file.c and dir.c.
> > This ioctl sends the nfs_fh to a userland application.
>
> Doesn't /proc/fs/nfsd/filehandle do what you want already?
>
> See nfs-util/utils/mountd/cache.c:cache_get_filehandle(), or, for the
> kernel side, linux/fs/nfsd/nfsctl.c:write_filehandle().
>
> (Just out of curiosity--why are you doing this?)
>
> --b.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in the body of a message to majordomo@vger.kernel.org More majordomo
> info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2007-02-13 23:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-11 8:06 Getting the nfs_fh of a specific file/dir from the kernel Menny Hamburger
2007-02-13 23:13 ` Trond Myklebust [this message]
2007-02-13 23:16 ` J. Bruce Fields
2007-02-13 23:19 ` Trond Myklebust
2007-02-13 23:36 ` J. Bruce Fields
-- strict thread matches above, loose matches on Subject: below --
2007-02-08 16:38 Menny Hamburger
2007-02-08 20:12 ` 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=1171408381.6031.1.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menny@exanet.com \
/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