Re: mlockall() still causes 100 % oops in 2.0.27

Zarmfab Software Development (
Tue, 3 Dec 1996 13:51:24 +0100

On Dec 1, 6:57pm, Ion Badulescu wrote:

> Could you please pipe the oops through ksymoops and post the results here?
> It might give somebody a clue about the pointer...

maybe it's easier to produce the oops: this is the source, compileable
under redhat-4.0.
It would be interesting to me if somebody is able to run the program without
oopsing, and under which kernel-version.

#include <unistd.h>
#include <string.h>
#include <stdio.h>
#include <sys/resource.h>
#include <sys/mman.h>
#include <asm/unistd.h>

#ifdef __alpha
#define _syscall1(type,name,type1,arg1) \
type name(type1 arg1) \
{ \
return syscall(__NR_##name, arg1); \


int main(int argc,char *argv[])

if (mlockall( MCL_CURRENT )) perror("mlockall");
return 0;

Martin Cornelius, ZARMFAB software development, University of Bremen
phone: 49-421-218-4807    FAX: 49-421-218-3889
paper-mail: Hochschulring / Am Fallturm, 28359 BREMEN, Germany