linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Castor Fu <castor@3pardata.com>
To: <linux-kernel@vger.kernel.org>
Subject: OOPS in ext3 kjournald -- 2.4.18
Date: Thu, 10 Apr 2003 16:55:40 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.33.0304101633300.12792-100000@marais> (raw)

We recently had a kernel OOPS accessing an ext3 filesystem using
kjournald on a system running 2.4.18 + our drivers.  We haven't seen this particular
OOPS before, and wanted to see if it was a known problem.

System: Dual processor Pentium-III

Thanks to LKCD, I've looked through the  buffer_head structure which looks
corrupted, but I haven't figured out why.  Suggestions are welcoe.

    Thanks!
    Castor Fu
    castor@3pardata.com

Traceback:

     #3 [52457e2c] page_fault (via error_code) at 401070fc
        EAX: 00002085  EBX: 00000003  ECX: 00000001  EDX: 00000001  EBP: 52457e2c
        DS:  0018      ESI: 00000009  ES:  0018      EDI: 00007000
        CS:  0010      EIP: 4013a323  ERR: ffffffff  EFLAGS: 00010202
     #4 [52457e2c] get_hash_table+115 at 4013a323
        (7000, 2085, 1000, 52a6b600, 5f8b2bb0)
     #5 [52457e4c] getblk at 4013ab8c
        (7000, 2085, 1000)
     #6 [52457e6c] journal_get_descriptor_buffer at 4016bd20
        (52a6b600)
     #7 [52457fc4] journal_commit_transaction at 40168d79
        (52a6b600)
     #8 [52457fec] kjournald at 4016b646
        (52a6b600)
     #9 [521c7dd8] kernel_thread at 40105690
        (0, 0, 0)

    crash> p *$bh
    $10 = {
      b_next = 0x1, b_blocknr = 8325, b_size = 28672, b_list = 26594, b_dev =
      28672, b_count = {
        counter = 0
      }, b_rdev = 28672, b_state = 25, b_flushtime = 0, b_next_free = 0x0,
      b_prev_free = 0x0, b_this_page = 0x52923f20, b_reqnext = 0x0, b_pprev
      = 0x418238a4, b_data = 0x47435000 "@;9\230", b_page = 0x411d0d40,
      b_end_io = 0x40168720 <journal_end_buffer_io_sync>, b_private = 0x0,
      b_rsector = 66600,
      b_wait = { lock = { lock = 1 },
    task_list = { next = 0x52923f6c, prev = 0x52923f6c } },
    b_inode = 0x0, b_inode_buffers = { next = 0x0, prev = 0x0 }
    }

b_next, b_size, and probably b_list are all corrupted.  We can compare the buffer
structures with that of the previous page:

    crash> x /24x $bh
    0x52923f20:     0x00000001      0x00002085      0x67e27000      0x00007000
    0x52923f30:     0x00000000      0x00007000      0x00000019      0x00000000
    0x52923f40:     0x00000000      0x00000000      0x52923f20      0x00000000
    0x52923f50:     0x418238a4      0x47435000      0x411d0d40      0x40168720
    0x52923f60:     0x00000000      0x00010428      0x00000001      0x52923f6c
    0x52923f70:     0x52923f6c      0x00000000      0x00000000      0x00000000

    crash> x /24x 0x52923e60
    0x52923e60:     0x00000000      0x00002084      0x00001000      0x00007000
    0x52923e70:     0x00000000      0x00007000      0x00000019      0x0018c78b
    0x52923e80:     0x00000000      0x00000000      0x52923e60      0x00000000
    0x52923e90:     0x41823084      0x4730c000      0x411cc300      0x40168720
    0x52923ea0:     0x00000000      0x00010420      0x00000001      0x52923eac
    0x52923eb0:     0x52923eac      0x00000000      0x57c7bdb8      0x57c7bdb8



                 reply	other threads:[~2003-04-10 23:44 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=Pine.LNX.4.33.0304101633300.12792-100000@marais \
    --to=castor@3pardata.com \
    --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;
as well as URLs for NNTP newsgroup(s).