From: Alex Zarochentsev <zam@namesys.com>
To: Alexander Gran <alex@zodiac.dnsalias.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: NULL pointe rin reiserfs
Date: Wed, 13 Apr 2005 17:54:38 +0400 [thread overview]
Message-ID: <20050413135438.GA6936@backtop.namesys.com> (raw)
In-Reply-To: <200504131217.17308@zodiac.zodiac.dnsalias.org>
hello,
On Wed, Apr 13, 2005 at 12:17:15PM +0200, Alexander Gran wrote:
> Hi,
>
> after resizing a reiserfs partition, the next cvs process produced:
please provide more information about the system (.config, h/w configuration)
and how the fs was resized. were there other error messages in the syslog
right before the crash?
may i guess -- was it online fs expanding with the cvs process running in
parallel?
> Unable to handle kernel NULL pointer dereference at virtual address 00000000
> printing eip:
> c0192701
> *pde = 00000000
> Oops: 0000 [#1]
> PREEMPT
> Modules linked in: usbserial md5 ipv6 sk98lin
> CPU: 0
> EIP: 0060:[<c0192701>] Not tainted VLI
> EFLAGS: 00010286 (2.6.10-rc1-k7-vrs1)
> EIP is at scan_bitmap_block+0x41/0x2c0
> eax: f2d0d000 ebx: c6630eac ecx: 00027305 edx: 00000000
> esi: f2d0d060 edi: c6630c48 ebp: eeeb3200 esp: c6630bdc
> ds: 007b es: 007b ss: 0068
> Process cvs (pid: 11807, threadinfo=c6630000 task=d7545ae0)
> Stack: 04040404 04040404 00005109 00184859 430034ec 00000800 542e1a94 3e846bff
> b75bcfc3 0000000c c6630c48 eeeb3200 00000000 c0192c57 c6630eac 0000000c
> c6630c48 00008000 00000002 00000002 00000001 eef8ce20 00007fff c6630d68
> Call Trace:
> [<c0192c57>] scan_bitmap+0x1d7/0x260
> [<c0193ea6>] reiserfs_allocate_blocknrs+0x196/0x4f0
> [<c01a15b2>] reiserfs_allocate_blocks_for_region+0x302/0x16d0
> [<c0139b18>] add_to_page_cache+0x68/0xc0
> [<c019b085>] make_cpu_key+0x55/0x60
> [<c01a39a3>] reiserfs_prepare_file_region_for_write+0x6b3/0xa10
> [<c01a42d5>] reiserfs_file_write+0x5d5/0x840
> [<c0149b73>] do_no_page+0x63/0x350
> [<c0117b80>] do_page_fault+0x3d0/0x5ee
> [<c015913e>] vfs_write+0xbe/0x130
> [<c0159281>] sys_write+0x51/0x80
> [<c010623b>] syscall_call+0x7/0xb
> Code: 3c 8b 28 8b 0f 8b 85 50 01 00 00 8b 40 08 89 4c 24 14 8b 4b 10 85 c9 8d
> 34 d0 0f 84 7c 02 00 00 85 f6 0f 84 5a 02 00 00 8b 56 04 <8b> 02 83 e0 04 0f
> 85 3f 02 00 00 8d 74 26 00 0f b7 46 02 3b 44
>
> regards
> Alex
> --
> Encrypted Mails welcome.
> PGP-Key at http://zodiac.dnsalias.org/misc/pgpkey.asc | Key-ID: 0x6D7DD291
--
Alex.
next prev parent reply other threads:[~2005-04-13 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 10:17 Alexander Gran
2005-04-13 13:54 ` Alex Zarochentsev [this message]
2005-04-13 15:34 ` Alexander Gran
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=20050413135438.GA6936@backtop.namesys.com \
--to=zam@namesys.com \
--cc=alex@zodiac.dnsalias.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
all inboxes | Powered by JetHome®