linux-kernel - Re: what is necessary for directory hard links

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] [day] [month] [year] [list]

Date:	Mon, 24 Jul 2006 10:42:28 +0400
From:	Nikita Danilov <nikita@...sterfs.com>
To:	"Joshua Hudson" <joshudson@...il.com>
Cc:	Linux Kernel Mailing List <Linux-Kernel@...r.Kernel.ORG>
Subject: Re: what is necessary for directory hard links

Joshua Hudson writes:
 > Some people seem to think that I am proposing to do something.
 > Understand that I have done it for 2.6.17-rc4 and am currently
 > involved in bringing it forward to newer kernels.
 > 
 > >
 > > What is the parent of a hard linked directory?  What is the parent if
 > > the link in "the parent" is deleted?
 > 
 > The parent is any and all directories that contain a link to the
 > stated directory.  ".." points back along the path the referrer used
 > to reach the current directory (this behavior is already in kernel:
 > didn't have to lift a finger to get it).

That won't work for kernel NFS server, using ->get_parent() method to
obtain parent directory.

Well... this is probably the smallest problem with hard-linked
directories, though.

Nikita.

-
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/