From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] UML + skas
Date: Tue, 30 Dec 2003 20:08:11 +0100 [thread overview]
Message-ID: <200312302008.11815.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <20031230183331.GB2845@carpediem.epita.fr>
Alle 19:33, martedì 30 dicembre 2003, jeremie le-hen ha scritto:
> Hi all,
> I have just subscribed to this list because I found a strange bug while
> compiling an UML within an SKAS'd host. Here is the problem :
>
> (my host is a 2.4.23 kernel with the SKAS patch released on 2002/11/11)
> After preprocessing the process.c file, I found that
> `struct ptrace_faultinfo' and `struct ptrace_ldt' were first defined
> in file `/usr/include/asm/ptrace.h' and then in
> `arch/um/include/skas_ptrace.h'.
> Since `/usr/include/asm/' is a symlink
> in `/usr/src/linux/` which in turn points to my kernel source,
Making /usr/include/asm a symlink into kernel sources is a very bad thing; if
your distro did this it's not your fault, but recent distros don't do this
from ages (neither RedHat nor Mandrake, at least, for what I saw).
>
> This is *exactly* the same content as `arch/um/include/skas_ptrace.h'.
> From what I googled, it seems to be a known bug. But it think it would
> not be very difficult to make some #define protection around theses
> structures to prevent from changing the destination of `/usr/src/linux/'
> to a source without the SKAS patch applied.
Yes, it wouldn't not hard.
But you should not use the same source tree to apply both patches. I think
this is explained very clearly and that the patches are not meant to be
compatible. Also, in that way you easily get into problems because
include/asm points to asm-i386 and is not updated to point to asm-um.
Also, if you make /usr/include/asm (this holds also for /usr/include/linux) a
symlink into kernel sources, that is not good.
And I don't think that any update to the host patch will ever be made
available, since Jeff Dike is making ready the SKAS 4 patch.
--
cat <<EOSIGN
Paolo Giarrusso, aka Blaisorblade
Linux Kernel 2.4.21/2.6.0-test on an i686; Linux registered user n. 292729
EOSIGN
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&opÌk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2003-12-30 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 18:33 [uml-devel] UML + skas jeremie le-hen
2003-12-30 19:08 ` BlaisorBlade [this message]
2004-01-06 2:58 ` Jeff Dike
2004-01-06 4:33 ` attriel
2004-01-06 20:42 ` jeremie le-hen
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=200312302008.11815.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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