From: Neil Brown <neilb@suse.de>
To: "Joshua Hudson" <joshudson@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: wait4/waitpid/waitid oddness
Date: Fri, 7 Apr 2006 16:50:35 +1000 [thread overview]
Message-ID: <17462.3003.229525.874004@cse.unsw.edu.au> (raw)
In-Reply-To: message from Joshua Hudson on Thursday April 6
On Thursday April 6, joshudson@gmail.com wrote:
> On 4/6/06, Kyle Moffett <mrmacman_g4@mac.com> wrote:
> > On Apr 6, 2006, at 22:09:48, Joshua Hudson wrote:
> > > I'm the guy who removed the check in link() about source is a
> > > directory, found out what broke, and am working on a patch to fix
> > > all the resulting breakage. Your task is apt to be a lot simpler.
> >
> > I seem to recall the reason why hardlinking directories was
> > prohibited had something more to do with some unfixable races and
> > deadlocks in the kernel; not to mention creating self-referential
> > directory trees that are never freed and chew up disk space.
>
> You recall correctly. I have fixed the self-referrential problem, and I
> am testing a fix for the races and deadlocks. Desk proof is not good
> enough for me.
I wonder what you are doing about the conceptual problem of
What does ".." mean now?
NeilBrown
next prev parent reply other threads:[~2006-04-07 6:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 3:38 wait4/waitpid/waitid oddness Albert Cahalan
2006-04-07 2:09 ` Joshua Hudson
2006-04-07 5:38 ` Kyle Moffett
2006-04-07 6:40 ` Joshua Hudson
2006-04-07 6:50 ` Neil Brown [this message]
2006-04-07 7:09 ` Joshua Hudson
2006-04-07 18:23 ` Eric W. Biederman
2006-04-07 18:58 ` Joshua Hudson
2006-04-07 19:19 ` Eric W. Biederman
2006-04-07 19:24 ` Joshua Hudson
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=17462.3003.229525.874004@cse.unsw.edu.au \
--to=neilb@suse.de \
--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).