mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Paul Mackerras <paulus@au1.ibm.com>,
	Fabrice Bellard <fabrice.bellard@free.fr>,
	linux-kernel@vger.kernel.org,
	Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: [PATCH] Qemu support for PPC
Date: Mon, 7 Apr 2003 07:56:22 +0100	[thread overview]
Message-ID: <20030407075622.A28354@infradead.org> (raw)
In-Reply-To: <20030407064541.4E1312C04E@lists.samba.org>; from rusty@rustcorp.com.au on Mon, Apr 07, 2003 at 04:45:33PM +1000

On Mon, Apr 07, 2003 at 04:45:33PM +1000, Rusty Russell wrote:
> Which simply shows that an entry in the MAINTAINERS file does not a
> maintainer make, since your first post showed such misundestanding of
> what personalities do,

oha,  just because I read the patch wrongly (I somehow though it added
a binary format)  I now don't understand the personalities at all?
Remember that I wrote most of the code that's now in kernel/exec_domain.c..

> and you've let the 2.4 and 2.5 personality
> lists get out of sync.

That's what's happening if people hack last minute changes into 2.4
instead of properly going through 2.5 and the maintainer.

> Qemu could hack it into all the stat, stat64, open, chmod, chown,
> link, rename etc. calls in the emulator, yes, but the in-kernel
> solution already exists and is far simpler.

The inkernel solution exists, and it's a bad (though valueable) hack.

> > Because stuff should go into 2.5 first.
> 
> I happens, though, whatever you may think.  It was done as a 2.4 patch
> because there's a tighter time constraint on entry into 2.4.

Umm, quemu exists for about two weeks now.  I think you're pressing
a bit too much.

Why is there a time constraint?  It worked for you up to now without
this patch in mainline and you can keep patching your trees for 2.4.21,
too.

> This is not qemu specific, of course.  If you say it's not going in,
> then I'll accept that and do the work inside qemu.  It'll be damn
> slow, of course.

Please try it in userspace first, if it's really not doable we can abuse
the kernel for it, but I'd prefer not doing it.  And if we need to do
it in the kernel we should think about a sys_altroot mechanism that doesn't
rely on the personality handling which isn't needed by qemu at all but
rather just exposes set_fs_altroot to userspace directly.  In fact that
sounds like a very good idea to start with.  What about hacking it up
for 2.5? :)


  reply	other threads:[~2003-04-07  6:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07  6:45 Rusty Russell
2003-04-07  6:56 ` Christoph Hellwig [this message]
2003-04-07  8:34   ` Rusty Russell
2003-04-07 12:49     ` Christoph Hellwig
2003-04-08  1:52       ` Rusty Russell
2003-04-07 11:21 ` Alan Cox
2003-04-09  2:07   ` Rusty Russell
  -- strict thread matches above, loose matches on Subject: below --
2003-04-07  2:40 Rusty Russell
2003-04-07  2:29 ` Paul Mackerras
2003-04-07  5:58 ` Christoph Hellwig
2003-04-07  5:09   ` Paul Mackerras
2003-04-07  6:21     ` Christoph Hellwig
2003-04-07  6:05       ` Paul Mackerras
2003-04-07 11:24         ` Alan Cox
2003-04-07 20:41 ` Tom Rini

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=20030407075622.A28354@infradead.org \
    --to=hch@infradead.org \
    --cc=fabrice.bellard@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=paulus@au1.ibm.com \
    --cc=rusty@rustcorp.com.au \
    /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

all inboxes | Powered by JetHome®