From: Al Viro <viro@ZenIV.linux.org.uk>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Best way of getting a pathname for error reporting?
Date: Fri, 20 Apr 2012 19:13:46 +0100 [thread overview]
Message-ID: <20120420181346.GJ6871@ZenIV.linux.org.uk> (raw)
In-Reply-To: <E1SLIG5-00028f-IV@tytso-glaptop.cam.corp.google.com>
On Fri, Apr 20, 2012 at 02:08:37PM -0400, Theodore Ts'o wrote:
> I wonder if we would be better off simply exporting dentry_path(),
> perhaps as EXPORT_SYMBOL_GPL, with a warning that it should only be used
> for debugging purposes, or some such. I suspect it's not worth changing
> all of the inode_ops interfaces to pass in a struct path intead of a
> struct dentry if it's only to be used for debugging. Or maybe I should
> just keep on doing these ugly things and justify them because it's only
> for debugging (yelch).
>
> What do you think?
Just use dentry_path_raw() - it _is_ exported and the only difference is
the lack of //deleted for unlinked ones.
prev parent reply other threads:[~2012-04-20 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 18:08 Best way of getting a pathname for error reporting? Theodore Ts'o
2012-04-20 18:13 ` Al Viro [this message]
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=20120420181346.GJ6871@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.