All of lore.kernel.org
 help / color / mirror / Atom feed
From: rwhron@earthlink.net
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: Oops on 2.5.1-pre6 doing mkreiserfs on loop device
Date: Fri, 7 Dec 2001 11:40:46 -0500	[thread overview]
Message-ID: <20011207114046.A152@earthlink.net> (raw)
In-Reply-To: <20011206233759.A173@earthlink.net> <20011207144836.GF12017@suse.de> <20011207145431.GI12017@suse.de> <20011207150058.GJ12017@suse.de>
In-Reply-To: <20011207150058.GJ12017@suse.de>; from axboe@suse.de on Fri, Dec 07, 2001 at 04:00:58PM +0100

On Fri, Dec 07, 2001 at 04:00:58PM +0100, Jens Axboe wrote:
> > argh, that should read 'i' and not '0' of course.
> 
> Updated patch follows.

I got a very similar oops during mkreiserfs /dev/loop0 on this
HIGHMEM machine.

Unable to handle kernel NULL pointer dereference at virtual address 00000018
c012b422
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c012b422>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010046
eax: 00000000   ebx: f7e7241c   ecx: 00000000   edx: 00000000
esi: 00000000   edi: 00000000   ebp: f7eaf280   esp: f7631f98
ds: 0018   es: 0018   ss: 0018
Process loop0 (pid: 131, stackpage=f7631000)
Stack: c012e5e5 f7630000 f7eaf2c0 f7651000 00000001 0000000c 00000286 00000000 
00000286 f7eaf280 c0134553 f7eaf2c0 00000008 fac2ec19 f7eaf2c0 00000001 
00000008 f7651000 f7eaf2c0 00000f00 f764ff2c f7651000 c01054e8 f7651000 
Call Trace: [<c012e5e5>] [<c0134553>] [<fac2ec19>] [<c01054e8>] 
Code: 8b 41 18 f6 c4 40 75 11 ff 49 14 0f 94 c0 84 c0 74 07 89 c8 

>>EIP; c012b422 <__free_pages+2/20>   <=====
Trace; c012e5e4 <bounce_end_io_read+144/1a0>
Trace; c0134552 <bio_endio+22/30>
Trace; fac2ec18 <[loop]loop_thread+c8/150>
Trace; c01054e8 <kernel_thread+28/40>
Code;  c012b422 <__free_pages+2/20>
00000000 <_EIP>:
Code;  c012b422 <__free_pages+2/20>   <=====
   0:   8b 41 18                  mov    0x18(%ecx),%eax   <=====
Code;  c012b424 <__free_pages+4/20>
   3:   f6 c4 40                  test   $0x40,%ah
Code;  c012b428 <__free_pages+8/20>
   6:   75 11                     jne    19 <_EIP+0x19> c012b43a <__free_pages+1a/20>
Code;  c012b42a <__free_pages+a/20>
   8:   ff 49 14                  decl   0x14(%ecx)
Code;  c012b42c <__free_pages+c/20>
   b:   0f 94 c0                  sete   %al
Code;  c012b430 <__free_pages+10/20>
   e:   84 c0                     test   %al,%al
Code;  c012b432 <__free_pages+12/20>
  10:   74 07                     je     19 <_EIP+0x19> c012b43a <__free_pages+1a/20>
Code;  c012b434 <__free_pages+14/20>
  12:   89 c8                     mov    %ecx,%eax

I eyeballed the patched source to verify it applied.  I noticed some of the 
lines in the patch have a \ at the end of line.  That may be irrelevant.

> +#define __bio_for_each_segment(bvl, bio, i, start_idx)			\
> +	for (bvl = bio_iovec((bio)), i = (start_idx);			\

Hope this helps.
-- 
Randy Hron


  reply	other threads:[~2001-12-07 16:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-07  4:37 Oops on 2.5.1-pre6 doing mkreiserfs on loop device rwhron
2001-12-07 14:48 ` Jens Axboe
2001-12-07 14:54   ` Jens Axboe
2001-12-07 15:00     ` Jens Axboe
2001-12-07 16:40       ` rwhron [this message]
2001-12-07 16:44         ` Jens Axboe
2001-12-07 17:36           ` rwhron
2001-12-09  8:07           ` rwhron
2001-12-09  8:57             ` Jens Axboe

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=20011207114046.A152@earthlink.net \
    --to=rwhron@earthlink.net \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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.