From: Nicholas Lee <nic-lists@plumtree.co.nz>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: skas and vserver on 2.4.25 (Re: [uml-devel] new skas3 patch ready for 2.4.25)
Date: Mon, 23 Feb 2004 19:30:21 +1300 [thread overview]
Message-ID: <20040223063021.GC31430@woodcut.kpac.co.nz> (raw)
In-Reply-To: <200402202125.58574.blaisorblade_spam@yahoo.it>
On Fri, Feb 20, 2004 at 09:25:57PM +0100, BlaisorBlade wrote:
>
> Yes, it went away, so a new skas patch must be built. I have one (tested) at
> http://www.user-mode-linux.org/~blaisorblade/
Using this patch against against 2.4.25 with evmns, libata and the
vserver patch, I get the following compilation error:-
nic@stateless:/usr/src/linux-2.4.25-vs1.3.7/mm$ gcc -D__KERNEL__ -I/usr/src/linux-2.4.25-vs1.3.7/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -nostdinc -iwithprefix include -DKBUILD_BASENAME=proc_mm -c -o proc_mm.o proc_mm.c
proc_mm.c: In function `open_proc_mm':
proc_mm.c:109: error: too few arguments to function `mm_alloc'
mm_alloc seems to come from:
<linux/sched.h>
...
extern struct mm_struct * mm_alloc(struct vx_info *);
vx_info is defined in <linux/vserver/context.h>
Looks like vserver has redefined:-
-extern struct mm_struct * mm_alloc(void);
+extern struct mm_struct * mm_alloc(struct vx_info *);
I don't know the kernel well enough to add the appropiate call to:
static int open_proc_mm(struct inode *inode, struct file *file)
{
struct mm_struct *mm = mm_alloc();
I'm guessing it might be something like
mm_alloc(current->vx_info);
--
Nicholas Lee - nj.lee at plumtree.co dot nz, somewhere on the fish Maui caught.
gpg. 8072 4F86 EDCD 4FC1 18EF 5BDD 07B0 9597 6D58 D70C
Quixotic Eccentricity
-------------------------------------------------------
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-23 6:38 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
2004-02-22 19:56 ` BlaisorBlade
2004-02-25 7:57 ` Nix
2004-02-23 6:30 ` Nicholas Lee [this message]
2004-02-25 15:54 ` skas and vserver on 2.4.25 (Re: [uml-devel] new skas3 patch ready for 2.4.25) 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=20040223063021.GC31430@woodcut.kpac.co.nz \
--to=nic-lists@plumtree.co.nz \
--cc=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