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

Date:	Sat, 22 Jul 2006 11:13:01 -0700
From:	"Joshua Hudson" <joshudson@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: what is necessary for directory hard links

On 7/22/06, Bodo Eggert <7eggert@...tempel.de> wrote:
> Horst H. von Brand <vonbrand@....utfsm.cl> wrote:
>
> > Joshua Hudson <joshudson@...il.com> wrote:
> >> This patch is the sum total of all that I had to change in the kernel
> >> VFS layer to support hard links to directories
> >
> > Can't be done, as it creates the possibility of loops.
>
> Don't do that then?
Exactly.

> > Detecting unconnected subgraphs uses a /lot/ of memory; and much worse, you
> > have to stop (almost) all filesystem activity while doing it.
I know.

I just decided the price is worth it.

In my filesystem, any attempt to create a loop of hard links
is detected and cancelled. Unlinking a directory requires it
to be empty if the last link is being removed. "." and ".."
links are counted separately from real links, so that is easy.
-
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/