From: Nix <nix@esperi.org.uk>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
user-mode-linux-user@lists.sourceforge.net
Subject: Re: [uml-user] Re: [uml-devel] new skas3 patch ready for 2.4.25
Date: Sun, 22 Feb 2004 18:04:43 +0000 [thread overview]
Message-ID: <87u11jrnwk.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <200402221516.09898.blaisorblade_spam@yahoo.it> (BlaisorBlade's message of "Sun, 22 Feb 2004 16:00:38 +0100")
On Sun, 22 Feb 2004, BlaisorBlade said:
> Hmmm, I've looked at the faulting code and IMHO the most probable thing is a
> compilation problem (forgot make dep after applying the patch, for instance) -
> try saving your .config, running make mrproper,
> grepping through .config to check that CONFIG_PROC_MM=y and recompiling the
> bzImage:
> $ make dep bzImage
It's highly plausible that exactly that happened: I forgot `make
oldconfig' during the first build and assumed (ha!) that `make dep'
would fix everything up OK so that a config change would trigger
rebuilds appropriately. Possibly this was a foolish assumption and a
`make dep clean' was necessary.
> More exactly, it seems that arch/i386/kernel/ptrace.c was recompiled after
> applying the patch but without CONFIG_PROC_MM on.
OK.
> Also, IMHO that kind of error cannot be returned by sys_ptrace, unless
> CONFIG_PROC_MM was off when compiling that file (I've also checked
> proc_mm_get_mm).
That's my conclusion too. I'll try rebuilding from scratch tomorrow
evening and see if that works.
(Oops.)
--
`note to the crown prosecution service: Machine guns dont have a
'stun' setting.' --- mjw
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
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:[~2004-02-22 18:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 16:00 [uml-devel] skas3 patch fails against vanilla-2.4.25 Patrick Moor
2004-02-19 20:27 ` [uml-devel] " Sven Köhler
2004-02-20 10:12 ` Gerd Knorr
2004-02-20 12:30 ` Sven Köhler
2004-02-20 12:54 ` Gerd Knorr
2004-02-20 13:19 ` Sven Köhler
2004-02-20 17:10 ` Goetz Bock
2004-02-20 20:25 ` [uml-devel] new skas3 patch ready for 2.4.25 BlaisorBlade
2004-02-21 15:50 ` Nix
2004-02-22 15:00 ` [uml-user] " BlaisorBlade
2004-02-22 18:04 ` Nix [this message]
2004-02-22 19:56 ` BlaisorBlade
2004-02-25 7:57 ` Nix
2004-02-23 6:30 ` skas and vserver on 2.4.25 (Re: [uml-devel] new skas3 patch ready for 2.4.25) Nicholas Lee
2004-02-25 15:54 ` BlaisorBlade
2004-02-25 19:40 ` Nicholas Lee
2004-02-25 20:06 ` BlaisorBlade
2004-02-24 15:59 ` [uml-devel] new skas3 patch ready for 2.4.25 Patrick Moor
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=87u11jrnwk.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=blaisorblade_spam@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@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