linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Horst H. von Brand" <vonbrand@inf.utfsm.cl>
To: "Joshua Hudson" <joshudson@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: what is necessary for directory hard links
Date: Fri, 21 Jul 2006 14:49:12 -0400	[thread overview]
Message-ID: <200607211849.k6LInCi8011368@laptop13.inf.utfsm.cl> (raw)
In-Reply-To: Your message of "Thu, 20 Jul 2006 18:04:49 MST." <bda6d13a0607201804je89fc3exd0b8f821509a3894@mail.gmail.com>

Joshua Hudson <joshudson@gmail.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. 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.

Besides, the flow "root down through directories" gives a natural order in
which to go locking stuff when needed; if there can be loops, the system
could easily deadlock.
-- 
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


  reply	other threads:[~2006-07-21 18:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-21  1:04 what is necessary for directory hard links Joshua Hudson
2006-07-21 18:49 ` Horst H. von Brand [this message]
2006-07-21 20:28 ` Rob Sims
2006-07-21 21:57   ` Joshua Hudson
2006-07-24  6:42     ` Nikita Danilov
     [not found] <6ARGK-19L-5@gated-at.bofh.it>
     [not found] ` <6B8og-1iB-17@gated-at.bofh.it>
2006-07-22 16:59   ` Bodo Eggert
2006-07-22 18:13     ` Joshua Hudson
2006-07-24  6:45       ` Nikita Danilov
2006-07-24  7:25         ` Valdis.Kletnieks
2006-07-24 16:21           ` Joshua Hudson
2006-07-24 17:55             ` Horst H. von Brand
2006-07-24 18:22             ` Valdis.Kletnieks
2006-07-25  4:49               ` Joshua Hudson
2006-07-25 12:43                 ` Valdis.Kletnieks
2006-07-25 14:47                 ` Horst H. von Brand
2006-07-23  2:19     ` Horst H. von Brand
2006-07-23 22:27       ` Vernon Mauery
2006-07-25 23:43       ` Peter Chubb
     [not found] <6CcT1-1lH-39@gated-at.bofh.it>
     [not found] ` <6Cwov-5xl-5@gated-at.bofh.it>
2006-07-25 21:28   ` Bodo Eggert
2006-07-26  1:00     ` Horst H. von Brand
2006-07-26  9:13       ` Bodo Eggert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200607211849.k6LInCi8011368@laptop13.inf.utfsm.cl \
    --to=vonbrand@inf.utfsm.cl \
    --cc=joshudson@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).