Assertion jfs_logmgr.c:2333 assert(bp->l_flag & lbmRELEASE)

Pedro Fonseca <[email protected]>
Newsgroups gmane.comp.file-systems.jfs.general
Message-ID <[email protected]>
Hi,

I've encountered a kernel bug that triggers an assertion in jfs_logmgr.c 
("assert(bp->l_flag & lbmRELEASE)") while running a custom test case on 
jfs (kernel 3.13.5), inside a QEMU based VM.

The assertion was triggered after doing two concurrent writes on 
different files located in the same directory.

Here's the system log output:
> [  244.458647] BUG at 
> /local/pfonseca/piking/kernel-build/linux-3.13.5-fs-static2/fs/jfs/jfs_logmgr.c:2333 
> assert(bp->l_flag & lbmRELEASE)
> [  244.458647] ------------[ cut here ]------------
> [  244.458647] kernel BUG at 
> /local/pfonseca/piking/kernel-build/linux-3.13.5-fs-static2/fs/jfs/jfs_logmgr.c:2333!
> [  244.458647] invalid opcode: 0000 [#1] SMP
> [  244.458647] Modules linked in: jfs loop rtc_cmos tpm_tis pcspkr 
> i2c_piix4
> [  244.458647] CPU: 1 PID: 2655 Comm: loop0 Not tainted 3.13.5 #2
> [  244.458647] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2007
> [  244.458647] task: c67645f0 ti: c6788000 task.ti: c6788000
> [  244.458647] EIP: 0060:[<e11bc4da>] EFLAGS: 00000046 CPU: 1
> [  244.458647] EIP is at lbmIODone+0x2c6/0x302 [jfs]
> [  244.458647] EAX: 0000007b EBX: cfb9bbc0 ECX: 00000093 EDX: 00000046
> [  244.458647] ESI: 00000297 EDI: c612a080 EBP: c6789ef8 ESP: c6789ecc
> [  244.458647]  DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
> [  244.458647] CR0: 8005003b CR2: b775d000 CR3: 01adb000 CR4: 00000690
> [  244.458647] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
> [  244.458647] DR6: 00000000 DR7: 00000000
> [  244.458647] Stack:
> [  244.458647]  e11c57b4 e11c5764 0000091d e11c58d8 e0eed3a5 12a02000 
> 00000000 cfbd5200
> [  244.458647]  cfbd5200 00000000 00000000 c6789f00 c10c78f2 c6789f68 
> e0eee04a c612a0c8
> [  244.458647]  cfbd531c e0eed36b cfa11bc0 00000001 12a02000 00000000 
> c612a080 cfbd5200
> [  244.458647] Call Trace:
> [  244.458647]  [<e0eed3a5>] ? do_lo_send_direct_write+0x3a/0x44 [loop]
> [  244.458647]  [<c10c78f2>] bio_endio+0x25/0x27
> [  244.458647]  [<e0eee04a>] loop_thread+0x402/0x426 [loop]
> [  244.458647]  [<e0eed36b>] ? __do_lo_send_write+0xbc/0xbc [loop]
> [  244.458647]  [<e0eedc48>] ? loop_attr_do_show_autoclear+0x12/0x12 
> [loop]
> [  244.458647]  [<c103e88e>] kthread+0x82/0x87
> [  244.458647]  [<c16b2b77>] ret_from_kernel_thread+0x1b/0x28
> [  244.458647]  [<c103e80c>] ? __kthread_parkme+0x50/0x50
> [  244.458647] Code: eb 04 83 66 78 fe 8b 55 e4 8b 45 ec eb 4c a8 04 
> 75 1b 68 d8 58 1c e1 68 1d 09 00 00 68 64 57 1c e1 68 b4 57 1c e1 e8 
> f2 b8 4e e0 <0f> 0b a8 10 75 1b 68 f0 58 1c e1 68 1e 09 00 00 68 64 57 
> 1c e1
> [  244.458647] EIP: [<e11bc4da>] lbmIODone+0x2c6/0x302 [jfs] SS:ESP 
> 0068:c6789ecc
> [  244.458647] ---[ end trace b54a6d87b1fd064d ]---


Pedro




------------------------------------------------------------------------------
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.