Re: what is necessary for directory hard links

["Horst H. von Brand" <vonbrand@inf.utfsm.cl>]

Bodo Eggert <7eggert@elstempel.de> wrote:
> Horst H. von Brand <vonbrand@inf.utfsm.cl> wrote:
> > Joshua Hudson <joshudson@gmail.com> wrote:
> 
> > [...]
> > 
> >> Maybe someday I'll work out a system by which much less is locked.
> >> Conceptually, all that is requred to lock for the algorithm
> >> to work is creating hard-links to directories and renaming directories
> >> cross-directory.
> > 
> > Some 40 years of filesystem development without finding a solution to that
> > conundrum would make that quite unlikely, but you are certainly welcome to
> > try.

> There is a simple solution against loops: No directory may contain a
> directory with a lower inode number.

This is a serious restriction...

> Off cause this would interfere with normal operations, so you'll allocate all
> normal inodes above e.g. 0x800000 and don't test between those inodes.

And allow loops there? I don't see how that solves anything...

> If you want to hardlink, you'll use a different (privileged) mkdir call
> that will allocate a choosen low inode number. This is also required for
> the parents of the hardlinked directories.

Argh... even /more/ illogical restrictions!

> You can also use the generic solution: Allow root to shoot his feet, and
> make sure the gun works correctly.

;-)
-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/