linux-ext4 - Re: uninit block group/mballoc and fsstress

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:	Wed, 10 Oct 2007 17:37:08 -0700
From:	Avantika Mathur <mathur@...ux.vnet.ibm.com>
To:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
CC:	linux-ext4 <linux-ext4@...r.kernel.org>
Subject: Re: uninit block group/mballoc and fsstress

Aneesh Kumar K.V wrote:
> I am hitting this with  the below config
>
> mke2fs -j -I 256 -O lazy_bg $dev
>
>
> mount -t ext4dev $dev /mnt/tmp -o "extents,mballoc"
>
> and running fsstress on /mnt/tmp/
I re-ran the test without the mballoc mount option, but with lazy_bg 
enabled, and saw the same error.   Error messages and stack are below.

mke2fs -j -I 256 -O lazy_bg $dev
mount -t ext4dev $dev /mnt/tmp -o "extents"

...

EXT4-fs error (device sda7) in ext4_reserve_inode_write: Journal has aborted

EXT4-fs error (device sda7) in ext4_dirty_inode: Journal has aborted

EXT4-fs error (device sda7) in ext4_new_blocks_old: Journal has aborted

EXT4-fs error (device sda7) in ext4_dirty_inode: Journal has aborted

EXT4-fs error (device sda7) in ext4_dirty_inode: Journal has aborted

EXT4-fs error (device sda7) in ext4_new_blocks_old: Journal has aborted

EXT4-fs error (device sda7) in ext4_new_blocks_old: Journal has aborted

EXT4-fs error (device sda7) in ext4_dirty_inode: Journal has aborted

EXT4-fs error (device sda7) in ext4_new_blocks_old: Journal has aborted

EXT4-fs error (device sda7) in ext4_dirty_inode: Journal has aborted

EXT4-fs error (device sda7) in ext4_new_blocks_old: Journal has aborted

Unable to handle kernel paging request for data at address 0x00000000

Faulting instruction address: 0xc0000000001af07c

cpu 0x2: Vector: 300 (Data Access) at [c0000000fdf4b9b0]

    pc: c0000000001af07c: .jbd2_journal_commit_transaction+0x11e8/0x1af4

    lr: c0000000001af05c: .jbd2_journal_commit_transaction+0x11c8/0x1af4

    sp: c0000000fdf4bc30

   msr: 8000000000009032

   dar: 0

 dsisr: 40000000

  current = 0xc0000000fc0f47f0

  paca    = 0xc000000000537880

    pid   = 5895, comm = kjournald2

enter ? for help

[c0000000fdf4be00] c0000000001b2994 .kjournald2+0xf4/0x2ac

[c0000000fdf4bf00] c00000000007afcc .kthread+0x84/0xd0

[c0000000fdf4bf90] c000000000027548 .kernel_thread+0x4c/0x68

2:mon>-- 0:conmux-control -- time-stamp -- Oct/10/07 11:28:02 --
-- 0:conmux-control -- time-stamp -- Oct/10/07 14:49:26 --
(bot:conmon-payload) disconnected

-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html