| 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
| ||
|
Date: Sat, 22 Jul 2006 18:59:45 +0200 From: Bodo Eggert <7eggert@...tempel.de> To: "Horst H. von Brand" <vonbrand@....utfsm.cl>, Joshua Hudson <joshudson@...il.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: what is necessary for directory hard links 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? > The "only files can > be hardlinked" idea makes garbage collection (== deleting of unreachable > objects) simple: Just check the number of references. > > Detecting unconnected subgraphs uses a /lot/ of memory; and much worse, you > have to stop (almost) all filesystem activity while doing it. In order to disconnect a directory, you'd have to empty it first, and after emptying a directory, it won't be part of a loop. Maybe emtying is the problem ... This feature was implemented, and I asume it was removed for a reason. Can somebody remember? -- Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF verbreiteten Lügen zu sabotieren. http://david.woodhou.se/why-not-spf.html - 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/
Powered by blists - more mailing lists