public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: LA Walsh <law@sgi.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: (struct dentry *)->vfsmnt;
Date: Fri, 09 Mar 2001 17:56:02 -0800	[thread overview]
Message-ID: <3AA989B2.9CE8273E@sgi.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0103091958030.17677-100000@weyl.math.psu.edu>

Alexander Viro wrote:
> No such thing. The same fs may be present in many places. Please,
> describe the situation - where do you get that dentry from?
>                                                         Cheers,
>                                                                 Al
---

Al,
	I'm getting it from various places, 1) if I want to know the
path relative to the root of the dentry at the end of 'path_walk'
or __user_path_walk (as used in truncate)  and
2) If I've gotten a dentry as in sys_fchdir/fchown/fstat/newfstat 
from a file descriptor and I want the absolute path or if multple
(such as multiple mounts of the same fs in different locations), the
one that the user used to access the dentry.

	In 2.2 there was a way to get the path only from the
dentry (d_path) -- I'm looking for similar functionality for the
above cases.

	Is it such that in 2.2 dentries were only relative to root
where in 2.4 they are relative to their mount point and instead of
duplicate dcache entries for each possible mount point, they get stored
as one?  

	If that's the case, then while I might get a path for user-path
walk, if I just have a 'fd', it may not be poasible to backtrace into
the path the user used to access the file?

	Just some wild speculations on my part....:-/...did
I refine the question enough?

thanks,
-linda


-- 
L A Walsh                        | Trust Technology, Core Linux, SGI
law@sgi.com                      | Voice: (650) 933-5338

  reply	other threads:[~2001-03-10  2:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-09 23:20 (struct dentry *)->vfsmnt; LA Walsh
2001-03-10  1:00 ` Alexander Viro
2001-03-10  1:56   ` LA Walsh [this message]
2001-03-10  2:42     ` Alexander Viro
2001-03-14  1:28       ` Andreas Dilger
2001-03-14  2:32         ` Alexander Viro
2001-03-14  4:27           ` Andreas Dilger
2001-03-14  5:11             ` Alexander Viro
2001-03-14  5:19               ` Andreas Dilger
2001-03-14  5:49                 ` Alexander Viro
2001-03-14  6:05                   ` Andreas Dilger
2001-03-14  6:50                     ` Alexander Viro
2001-03-14 17:26                       ` Andreas Dilger
2001-03-14 17:40                         ` Matthew Wilcox
2001-03-14 18:06                           ` Andreas Dilger
2001-03-14 18:11                         ` Alexander Viro
2001-03-14 19:14                           ` Andreas Dilger
2001-03-14 19:32                             ` Alexander Viro
2001-03-14 20:21                               ` Ragnar Kjørstad
2001-03-14 19:31                         ` Dave Kleikamp
2001-03-14 19:45                           ` Andreas Dilger
2001-03-14 19:51                             ` Alexander Viro
2001-03-14 19:57                             ` Dave Kleikamp
2001-03-14 21:07                               ` Andreas Dilger
  -- strict thread matches above, loose matches on Subject: below --
2001-03-15 12:21 bsuparna
2001-03-15 12:59 bsuparna

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=3AA989B2.9CE8273E@sgi.com \
    --to=law@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.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