linux-um archives
 help / color / mirror / Atom feed
From: Matt Zimmerman <mdz@debian.org>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Host panic triggered by UML
Date: Thu, 20 Nov 2003 15:06:11 -0500	[thread overview]
Message-ID: <20031120200611.GK9377@dijkstra.csh.rit.edu> (raw)
In-Reply-To: <200311201915.29188.blaisorblade_spam@yahoo.it>

On Thu, Nov 20, 2003 at 07:15:29PM +0100, BlaisorBlade wrote:

> Nov 19 04:40:24 blaisorblade kernel: Unable to handle kernel NULL pointer 
> dereference at virtual address 00000000
> Nov 19 04:40:24 blaisorblade kernel:  printing eip:
> Nov 19 04:40:24 blaisorblade kernel: c015421b
> Nov 19 04:40:24 blaisorblade kernel: *pde = 00000000
> Nov 19 04:40:24 blaisorblade kernel: Oops: 0002
> Nov 19 04:40:24 blaisorblade kernel: CPU:    0
> Nov 19 04:40:24 blaisorblade kernel: EIP:    0010:[dcache_dir_lseek+299/384]    
> Tainted: PF
> Nov 19 04:40:24 blaisorblade kernel: EIP:    0010:[<c015421b>]    Tainted: PF
> Nov 19 04:40:24 blaisorblade kernel: EFLAGS: 00010286
> Nov 19 04:40:24 blaisorblade kernel: eax: 00000000   ebx: c0d24160   ecx: 
> d6b15f08   edx: c0d24160
> Nov 19 04:40:24 blaisorblade kernel: esi: 00000002   edi: 00000000   ebp: 
> c0d24140   esp: d67cbf84
> Nov 19 04:40:24 blaisorblade kernel: ds: 0018   es: 0018   ss: 0018
> Nov 19 04:40:24 blaisorblade kernel: Process linux (pid: 18847, 
> stackpage=d67cb000)
> Nov 19 04:40:24 blaisorblade kernel: Stack: fffffff2 c0d24140 00000000 
> 00000000 c01540f0 d2473f20 c01433f8 d2473f20 
> Nov 19 04:40:24 blaisorblade kernel:        00000002 00000000 00000000 
> d67ca000 4014b008 00000002 a2533abc c01075b7 
> Nov 19 04:40:24 blaisorblade kernel:        0000002f 00000002 00000000 
> 4014b008 00000002 a2533abc 00000013 0000002b 
> Nov 19 04:40:24 blaisorblade kernel: Call Trace:    [dcache_dir_lseek+0/384] 
> [sys_lseek+120/192] [system_call+51/56]
> Nov 19 04:40:24 blaisorblade kernel: Call Trace:    [<c01540f0>] [<c01433f8>] 
> [<c01075b7>]
> Nov 19 04:40:24 blaisorblade kernel: 
> Nov 19 04:40:24 blaisorblade kernel: Code: 89 10 89 42 04 b8 00 e0 ff ff 21 e0 
> ff 48 04 8b 50 14 39 50 

I've seen this same crash many times; I sent it to lkml but got no response.

> (I've had another oops in the same call path and point, so I guess this
> was the reason even the other time).
> 
> This means that it crashes in fs/readdir.c:dcache_dir_lseek; after some
> checks So, probably the oops happened while working on that folder: what
> needs to be checked is if the tmpfs code creates an inconsistent
> list(exactly, an inconsistent struct dentry.d_subdirs one, since p walks
> into it). Do you think this is reasonable or not?

It only happened for me using UML hostfs on a tmpfs filesystem, so I believe
it is a tmpfs bug, yes.

-- 
 - mdz


-------------------------------------------------------
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

      parent reply	other threads:[~2003-11-20 20:06 UTC|newest]

Thread overview: 10+ 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   ` [uml-devel] Host panic when UML reads host /dev/shm BlaisorBlade
2003-11-20 22:32     ` 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 ` Matt Zimmerman [this message]

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=20031120200611.GK9377@dijkstra.csh.rit.edu \
    --to=mdz@debian.org \
    --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