From: Jeff Dike <jdike@addtoit.com>
To: M A Young <m.a.young@durham.ac.uk>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Kernel panic: Kernel mode fault at addr 0x0, ip 0x8053457
Date: Thu, 04 Sep 2003 15:55:26 -0400 [thread overview]
Message-ID: <200309041955.h84JtREX018760@uml.karaya.com> (raw)
In-Reply-To: Your message of "Thu, 04 Sep 2003 19:03:35 BST." <Pine.GSO.4.53.0309041857190.21341@altair.dur.ac.uk>
m.a.young@durham.ac.uk said:
> Jeff, we worked out what the bug was. His old selinux used syscall
> 223, which was completely uninitialized (ie. not even set to
> sys_ni_syscall), hence the kernel crashed. I was having the same
> problem in a different context with get_thread_area and
> set_thread_area.
Oops, looks like I missed that. Easily fixed, it looks like those were
NULL-filled holes in sys_call_table. The system call dispatcher did range
checking on the syscall number, but didn't see if the entry itself contained
anything.
And it looks like I missed some system calls that i386 has.
Jeff
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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-09-04 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 18:03 [uml-devel] Kernel panic: Kernel mode fault at addr 0x0, ip 0x8053457 M A Young
2003-09-04 19:55 ` Jeff Dike [this message]
2003-09-05 2:10 ` Jeff Dike
[not found] <200308201554.54799.russell@coker.com.au>
2003-09-04 17:09 ` Jeff Dike
2003-09-05 2:35 ` Russell Coker
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=200309041955.h84JtREX018760@uml.karaya.com \
--to=jdike@addtoit.com \
--cc=m.a.young@durham.ac.uk \
--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