From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Host panic when UML reads host /dev/shm
Date: Thu, 20 Nov 2003 20:37:14 +0100 [thread overview]
Message-ID: <200311202037.14480.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <200311201956.39623.Frank.dekervel@student.kuleuven.ac.Be>
Alle 19:56, giovedì 20 novembre 2003, Frank Dekervel ha scritto:
> Op Thursday 20 November 2003 19:15, schreef BlaisorBlade:
> > I reported that if I leave an UML sleeping, it segfaults(once I saw the
> > killed by SIGSEGV from the shell, the other time nothing, maybe I had
> > detached the job from the shell).
> >
> > Now I've seen that what happens is that the host kernel oopses. I'm
> > posting it here to collect a bit more infos before posting it to the
> > LKML, and to know why only UML is able to trigger it. Since the bug seems
> > related only to /dev/shm, maybe you could have some enlightenment about
> > it and how UML uses shared memory to make this happen.
>
> i saw the same crash.
Only an oops on linux or the same oops? If the second, it's useful news
> i worked around it by not using hostfs ...
So, probably there was a process runned from inside UML triggering the bug.
In fact, I'm seeing now 4:40, the time the oops happens, is when the slackware
every day runs updatedb.
A little transcript from a UML session:
root [~: slack90: 1 (0)] # mount
/dev/ubda on / type ext3 (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
proc on /proc type proc (rw)
host on /mnt/host type hostfs (rw,/)
root [~: slack90: 1 (0)] # ls /mnt/host/dev/sh
sheep_net shm shmiq
root [~: slack90: 1 (0)] # ls /mnt/host/dev/shm
<Pause because of the same host kernel oops.>
The host shell reported Segmentation fault(wrongly), so all the crashes I had
were due to this. I can even get the processes in D state(even a ls /dev/shm
suffices).
Thanks, Frank. Your message was very useful and enlightening.
I think hostfs reads files just as any normal process on the host, right? Or
it does anything special or at least unusual?
Could the unusual thing be the context switching of SKAS?
I'll test if it happens within TT mode. Jeff, this seems easy reproduceable,
so try it, please.
Bye
--
cat <<EOSIGN
Paolo Giarrusso, aka Blaisorblade
Linux Kernel 2.4.21/2.6.0-test on an i686; Linux registered user n. 292729
EOSIGN
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
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-11-20 19:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 18:15 [uml-devel] Host panic triggered by UML BlaisorBlade
2003-11-20 18:56 ` Frank Dekervel
2003-11-20 19:37 ` BlaisorBlade [this message]
2003-11-20 22:32 ` [uml-devel] Host panic when UML reads host /dev/shm Frank Dekervel
2003-11-20 22:47 ` Frank Dekervel
2003-11-22 18:11 ` BlaisorBlade
2003-11-24 3:36 ` Frank Dekervel
2003-11-21 2:22 ` Jeff Dike
2003-11-22 18:12 ` BlaisorBlade
2003-11-20 20:06 ` [uml-devel] Host panic triggered by UML Matt Zimmerman
-- strict thread matches above, loose matches on Subject: below --
2003-11-23 23:08 [uml-devel] Host panic when UML reads host /dev/shm James W McMechan
2003-11-25 3:02 James W McMechan
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=200311202037.14480.blaisorblade_spam@yahoo.it \
--to=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