From: Lars Marowsky-Bree <lmb@suse.de>
To: Oleg Drokin <green@linuxhacker.ru>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] "Kernel panic: Segfault with no mm"
Date: Tue, 9 Sep 2003 21:34:37 +0200 [thread overview]
Message-ID: <20030909193437.GE10485@marowsky-bree.de> (raw)
In-Reply-To: <200309091914.h89JE6ja000983@car.linuxhacker.ru>
On 2003-09-09T23:14:06,
Oleg Drokin <green@linuxhacker.ru> said:
> LMB> #5 <signal handler called>
>
> This is signal kernel and one step up is your buggy code.
> You just need to go up to that point to see what's wrong.
Yes, I know that, too.
But on the host, I'd get a panic which said which kernel module caused
it etc. Is that not to be expected in UML?
If all kernel segvs in UML would lead to this, why is the
if (!is_user) ... branch in the segv() in trap_kern.c there anyway?
It looks like a kernel mode fault should also be handled differently,
and like the Segfault with no mm is sort of an exception.
Sorry if I'm wrong, but I am trying to understand what's going on ;-)
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering ever tried. ever failed. no matter.
SuSE Labs try again. fail again. fail better.
Research & Development, SuSE Linux AG -- Samuel Beckett
-------------------------------------------------------
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-09 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 18:01 [uml-devel] "Kernel panic: Segfault with no mm" Lars Marowsky-Bree
2003-09-09 19:14 ` Oleg Drokin
2003-09-09 19:34 ` Lars Marowsky-Bree [this message]
2003-09-09 22:33 ` Jeff Dike
2003-09-10 7:49 ` Lars Marowsky-Bree
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=20030909193437.GE10485@marowsky-bree.de \
--to=lmb@suse.de \
--cc=green@linuxhacker.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.