From: Hans Reiser <reiser@namesys.com>
To: Chris Mason <mason@suse.com>
Cc: reiserfs-list@namesys.com
Subject: Re: reiser4 oops on unmount
Date: Tue, 24 Aug 2004 11:18:37 -0700 [thread overview]
Message-ID: <412B867D.4090801@namesys.com> (raw)
In-Reply-To: <1093361937.12138.3263.camel@watt.suse.com>
Chris Mason wrote:
>Hello everyone,
>
>I was testing reiser4 in the suse kernel and hit an oops during
>unmount. This could be a problem with my local merge, but I wanted to
>send here in case it is obvious.
>
>The workload was create a few files and dirs, delete them, create 1
>million files in a single dir, sync, unmount.
>
>Unable to handle kernel NULL pointer dereference at virtual address 00000010
> printing eip:
>f8a1826c
>*pde = 00000000
>Oops: 0000 [#1]
>SMP
>Modules linked in: reiser4 dm_mod
>CPU: 0
>EIP: 0060:[<f8a1826c>] Tainted: G U
>EFLAGS: 00010246 (2.6.8-0-testing)
>EIP is at safe_link_locality+0xc/0x30 [reiser4]
>eax: 00000000 ebx: 00000000 ecx: 00000000 edx: 00000000
>esi: d6a83340 edi: d6a83340 ebp: e65f7c94 esp: e65f7c90
>ds: 007b es: 007b ss: 0068
>Process umount (pid: 13346, threadinfo=e65f6000 task=f755d2d0)
>Stack: 00000000 e65f7cb4 f8a182be e65f7cbc 00000000 d6a83340 04271204 d6a83340
> d6a83340 e65f7ce4 f8a184a6 00000000 00000000 00000000 00000000 00000000
> 00000000 00000000 00000000 04271204 00000000 e65f7d20 f8a19cae 00000000
>Call Trace:
> [<c0106ed6>] show_stack+0xa6/0xb0
> [<c0107057>] show_registers+0x157/0x1c0
> [<c01071ec>] die+0x9c/0x160
> [<c011726c>] do_page_fault+0x3cc/0x53b
> [<c0106b4d>] error_code+0x2d/0x38
> [<f8a182be>] build_link_key+0x2e/0xa0 [reiser4]
> [<f8a184a6>] safe_link_del+0x16/0x30 [reiser4]
> [<f8a19cae>] common_object_delete_no_reserve+0xee/0x120 [reiser4]
> [<f8a19d3e>] delete_object+0x5e/0x70 [reiser4]
> [<f8a101e7>] reiser4_delete_inode+0x67/0x70 [reiser4]
> [<f8a1a67b>] delete_inode_common+0xdb/0x2c0 [reiser4]
> [<f8a1a8af>] drop_common+0x3f/0x50 [reiser4]
> [<f8a0ffb9>] reiser4_drop_inode+0x19/0x30 [reiser4]
> [<c0180716>] iput+0x56/0x80
> [<c017bc1f>] dput+0x8f/0x320
> [<c017c5bd>] prune_dcache+0x20d/0x370
> [<c017ccbd>] shrink_dcache_parent+0xd/0x20
> [<c0168bda>] generic_shutdown_super+0x2a/0x260
> [<c0169f2a>] kill_block_super+0x1a/0x40
> [<c0168a08>] deactivate_super+0x68/0xa0
> [<c01835a9>] sys_umount+0x59/0x80
> [<c01835e9>] sys_oldumount+0x19/0x20
> [<c0106071>] sysenter_past_esp+0x52/0x71
>Code: 8b 48 10 8b 81 50 ff ff ff 8b 49 20 89 c2 31 c0 09 da 09 c8
>
>
>
>
>
>
the guys will look at this on thursday, we need to get some billable
hours in on digeo work for me to make payroll.
next prev parent reply other threads:[~2004-08-24 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 15:38 reiser4 oops on unmount Chris Mason
2004-08-24 18:18 ` Hans Reiser [this message]
2004-08-25 13:14 ` Nikita Danilov
-- strict thread matches above, loose matches on Subject: below --
2004-08-25 2:12 David Dabbs
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=412B867D.4090801@namesys.com \
--to=reiser@namesys.com \
--cc=mason@suse.com \
--cc=reiserfs-list@namesys.com \
/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.