From: David Ford <david+cert@blue-labs.org>
To: linux-kernel@vger.kernel.org
Subject: [OOPS] Unable to handle kernel NULL pointer deref.. 2.4.19-pre6
Date: Sat, 13 Apr 2002 15:31:17 -0400 [thread overview]
Message-ID: <3CB88785.2060109@blue-labs.org> (raw)
Unable to handle kernel NULL pointer dereference at virtual address 00000132
c01497b8
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c01497b8>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010202
eax: ccd519d4 ebx: c27bde74 ecx: 00000000 edx: c27bde74
esi: 00000100 edi: 00000000 ebp: 00000001 esp: c968df88
ds: 0018 es: 0018 ss: 0018
Process mozilla-bin (pid: 217, stackpage=c968d000)
Stack: c27bde74 00000000 41b22e90 bffff0e8 c013553d 00000000 c27bde74
00000000
c27bde74 00000049 c01355b3 c27bde74 cb99b898 c968c000 c0108a9b
00000049
00000001 4020b858 00000049 41b22e90 bffff0e8 00000006 c010002b
0000002b
Call Trace: [<c013553d>] [<c01355b3>] [<c0108a9b>]
Code: 0f b7 46 32 25 00 f0 00 00 66 3d 00 40 74 0a b8 ec ff ff ff
>>EIP; c01497b8 <fcntl_dirnotify+28/170> <=====
Trace; c013553d <filp_close+2d/60>
Trace; c01355b3 <sys_close+43/50>
Trace; c0108a9b <system_call+33/38>
Code; c01497b8 <fcntl_dirnotify+28/170>
00000000 <_EIP>:
Code; c01497b8 <fcntl_dirnotify+28/170> <=====
0: 0f b7 46 32 movzwl 0x32(%esi),%eax <=====
Code; c01497bc <fcntl_dirnotify+2c/170>
4: 25 00 f0 00 00 and $0xf000,%eax
Code; c01497c1 <fcntl_dirnotify+31/170>
9: 66 3d 00 40 cmp $0x4000,%ax
Code; c01497c5 <fcntl_dirnotify+35/170>
d: 74 0a je 19 <_EIP+0x19> c01497d1
<fcntl_dirnotify+41/170>
Code; c01497c7 <fcntl_dirnotify+37/170>
f: b8 ec ff ff ff mov $0xffffffec,%eax
reply other threads:[~2002-04-13 19:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3CB88785.2060109@blue-labs.org \
--to=david+cert@blue-labs.org \
--cc=linux-kernel@vger.kernel.org \
/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