linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Ashish Khurange <ashishk@it.iitb.ac.in>
Cc: Shaya Potter <spotter@cs.columbia.edu>, linux-fsdevel@vger.kernel.org
Subject: Re: get vfsmount from dentry
Date: Sun, 12 Mar 2006 19:13:19 +0000	[thread overview]
Message-ID: <20060312191319.GE27946@ftp.linux.org.uk> (raw)
In-Reply-To: <44146E7E.8090902@it.iitb.ac.in>

On Mon, Mar 13, 2006 at 12:24:54AM +0530, Ashish Khurange wrote:
> In few functions (like sys_fchmod) I have file struct as an argument, 
> which provides me both vfsmount and dentry, hence I can find out 
> pathname of the file being changed.
> Where as in few functions (like vfs_mkdir) I have only dentry and inode 
> of the directory, which are not sufficient to find the pathname.
> 
> I hope I am clear now.

mkdir /tmp/1
mkdir /tmp/2
mkdir /tmp/3
mount --bind /tmp/2 /tmp/1
mkdir /tmp/1/a
umount /tmp/1
mount --bind /tmp/3 /tmp/1
mkdir /tmp/1/a
umount /tmp/1

What output do you want to get from the last two mkdir() calls, assuming
you do have vfsmounts?  What is this output useful for?

  reply	other threads:[~2006-03-12 19:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-12 13:44 get vfsmount from dentry Ashish Khurange
2006-03-12 13:55 ` Al Viro
2006-03-12 17:20   ` Ashish Khurange
2006-03-12 17:41     ` Al Viro
2006-03-12 18:00       ` Ashish Khurange
2006-03-12 18:23         ` Shaya Potter
2006-03-12 18:54           ` Ashish Khurange
2006-03-12 19:13             ` Al Viro [this message]
2006-03-12 20:34               ` Ashish Khurange
2006-03-12 20:45                 ` Shaya Potter
2006-03-13  7:24                 ` Jan Hudec
2006-03-12 18:24         ` Al Viro
2006-03-12 19:10 ` Jamie Lokier

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=20060312191319.GE27946@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=ashishk@it.iitb.ac.in \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=spotter@cs.columbia.edu \
    /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;
as well as URLs for NNTP newsgroup(s).