From: Christoph Hellwig <hch@ns.caldera.de>
To: David Mosberger <davidm@hpl.hp.com>
Cc: viro@math.psu.edu, torvalds@transmeta.com,
linux@arm.linux.org.uk, ralf@gnu.ai.mit.edu,
linux-kernel@vger.kernel.org, linux-ia64@linuxia64.org
Subject: Re: [Linux-ia64] __emul_prefix() problem
Date: Tue, 18 Sep 2001 12:23:15 +0200 [thread overview]
Message-ID: <20010918122314.A7015@caldera.de> (raw)
In-Reply-To: <200109172351.QAA29928@napali.hpl.hp.com>
In-Reply-To: <200109172351.QAA29928@napali.hpl.hp.com>; from davidm@hpl.hp.com on Mon, Sep 17, 2001 at 04:51:11PM -0700
On Mon, Sep 17, 2001 at 04:51:11PM -0700, David Mosberger wrote:
> I'm not sure there is a clean fix to this, but one proposal is
> attached below: it causes __emul_lookup_dentry() to ignore the
> alternate root for paths that resolve to a directory. This obviously
> could create other problems, but I suspect there is no solution that
> works 100% in all cases (the fundamental being that we now have two
> different root nodes...).
Looks sant to me and doesn't break Linux-ABI. For 2.5 I'd prefer
to somehow build a per-personality namespace. Al, do you have an
idea how to keep a secondary namespace alive over the whole uptime
so non-Linu binaries can switch to it all the time (implicitly)?
Christoph
next prev parent reply other threads:[~2001-09-18 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-17 23:51 __emul_prefix() problem David Mosberger
2001-09-18 10:23 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-17 23:51 [Linux-ia64] " David Mosberger
2001-09-18 10:23 ` Christoph Hellwig
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=20010918122314.A7015@caldera.de \
--to=hch@ns.caldera.de \
--cc=davidm@hpl.hp.com \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=ralf@gnu.ai.mit.edu \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.