linux-ext4 - Re: EXT4: kernel BUG at fs/jbd2/commit.c:533!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 04 Sep 2009 10:30:06 +0530
From:	Sachin Sant <sachinp@...ibm.com>
To:	Theodore Tso <tytso@....edu>
CC:	Andreas Dilger <adilger@....com>, linux-ext4@...r.kernel.org,
	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
Subject: Re: EXT4: kernel BUG at fs/jbd2/commit.c:533!

Sachin Sant wrote:
> As for this issue not sure how to proceed further. I probably will
> continue to execute the tests few more times. Maybe will try on
> a different box.
After increasing nproc value from 50 to 150 (-p 150)
i was able to recreate this bug again.

------------[ cut here ]------------
cpu 0x0: Vector: 700 (Program Check) at [c0000000fedeb970]
    pc: c000000000280f74: .jbd2_journal_commit_transaction+0x91c/0x1c6c
    lr: c000000000280f5c: .jbd2_journal_commit_transaction+0x904/0x1c6c
    sp: c0000000fedebbf0
   msr: 8000000000029032
  current = 0xc00000005e550c20
  paca    = 0xc000000000b62600
    pid   = 13149, comm = kjournald2
kernel BUG at fs/jbd2/commit.c:542!
enter ? for help
[c0000000fedebdd0] c000000000289cac .kjournald2+0x198/0x46c
[c0000000fedebed0] c0000000000a86a0 .kthread+0xac/0xb8
[c0000000fedebf90] c00000000002ab3c .kernel_thread+0x54/0x70
0:mon> dl

The change in line number for commit.c (533 to 542) is because of
some debug printk's i added in that file. Here are some of the
last few statements from dmesg buffer.

<6>EXT4-fs: mballoc enabled
<6>EXT4-fs (sda4): mounted filesystem with journalled data mode
<4>JBD: Spotted dirty metadata buffer (dev = sda4, blocknr = 1089515). There's a risk of filesystem corruption in case of system crash.
<4>JBD: Spotted dirty metadata buffer (dev = sda4, blocknr = 1089516). There's a risk of filesystem corruption in case of system crash.
<4>JBD: Spotted dirty metadata buffer (dev = sda4, blocknr = 1089517). There's a risk of filesystem corruption in case of system crash.
<4>JBD: Spotted dirty metadata buffer (dev = sda4, blocknr = 1089518). There's a risk of filesystem corruption in case of system crash.
<1>nr_buffers = 1560
<1>outstanding_credits = 1557
<1>state = 4
<1>state = 4
<1>start = 4300814543
<1>updates = 0
<0>------------[ cut here ]------------
<2>kernel BUG at fs/jbd2/commit.c:542!

The nr_buffers value was 1560 while that of t_outstanding_credits was 1557.

Let me know if i can provide any other information to
debug this issue. Have attached dmesg log.

Thanks
-Sachin

-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------

View attachment "log" of type "text/plain" (18015 bytes)