linux-kernel - Re: encode_fh: have inode but no dentry

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110224212317.GD22723@ZenIV.linux.org.uk>
Date:	Thu, 24 Feb 2011 21:23:17 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Dan Magenheimer <dan.magenheimer@...cle.com>
Cc:	aneesh.kumar@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org
Subject: Re: encode_fh: have inode but no dentry

On Thu, Feb 24, 2011 at 01:16:34PM -0800, Dan Magenheimer wrote:
> Hi Aneesh --
> 
> I see you are continuing with encode_fh related
> development so I thought I would bring this up
> with you.
> 
> I have a need to call the encode_fh op in a
> situation where I have an inode but not a dentry,
> and calling d_find_alias(inode) sometimes returns
> NULL.  In my usage, connectable is always zero, so
> having just the inode should be sufficient to get
> useful results from encode_fh, at least for the
> filesystems I've looked at.

[snip]

> Such a change would require a patch that touched
> nearly every filesystem so it's clearly not to
> be taken lightly.
> 
> Any thoughts on this?

How about "tell us what do you need that for", for starters?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/