linux-kernel - Re: 2.6.19-rc4-mm2 -- reiserfs umount panic

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20061103110210.08169843.akpm@osdl.org>
Date:	Fri, 3 Nov 2006 11:02:10 -0800
From:	Andrew Morton <akpm@...l.org>
To:	Andy Whitcroft <apw@...dowen.org>
Cc:	reiserfs-dev@...esys.com, linux-kernel@...r.kernel.org,
	reiserfs-list@...esys.com, Vasily Averin <vvs@...ru>
Subject: Re: 2.6.19-rc4-mm2 -- reiserfs umount panic

On Fri, 03 Nov 2006 15:08:06 +0000
Andy Whitcroft <apw@...dowen.org> wrote:

> Just happened to be watching a console of a test box when it was
> performing a post job reboot and caught the following panic.  This
> specific machine is a ppc64.  Sadly these are not part of the job.
> 
> /me considers how we could fix that.  Perhaps we could just shove a
> plain reboot at the end of one of the jobs ... hmmm.
> 
> -apw
> 
> REISERFS: panic (device sda3): journal_begin called without kernel lock held
> kernel BUG in reiserfs_panic at fs/reiserfs/prints.c:361!
> Oops: Exception in kernel mode, sig: 5 [#1]
> SMP NR_CPUS=32 NUMA
> Modules linked in:
> NIP: C000000000125A60 LR: C000000000125A5C CTR: 00000000000D0274
> REGS: c00000076e693640 TRAP: 0700   Not tainted  (2.6.19-rc4-mm2-autokern1)
> MSR: 8000000000029032 <EE,ME,IR,DR>  CR: 22008424  XER: 00000000
> TASK = c00000003fb68250[16416] 'umount' THREAD: c00000076e690000 CPU: 2
> GPR00: C000000000125A5C C00000076E6938C0 C0000000006662E8 0000000000000050
> GPR04: 0000000000000000 FFFFFFFFFFFFFFFF 656C206C6F636B20 68656C640D0A726E
> GPR08: 0000000000000000 C00000000054EAB8 C00000000068F810 C00000000068F808
> GPR12: 00000000000D0274 C000000000545500 0000000000000000 0000000000000000
> GPR16: 00000000100A7D10 00000000100A94E0 0000000010070000 0000000000000000
> GPR20: 0000000010010000 00000000FFFFFFFF 0000000010019218 0000000000000000
> GPR24: 0000000000000000 000000000000000A C00000076E693BC0 000000000000000A
> GPR28: C000000000518800 C00000076E693BC0 C000000000579080 C000000000518800
> NIP [C000000000125A60] .reiserfs_panic+0x6c/0x90
> LR [C000000000125A5C] .reiserfs_panic+0x68/0x90
> Call Trace:
> [C00000076E6938C0] [C000000000125A5C] .reiserfs_panic+0x68/0x90 (unreliable)
> [C00000076E693940] [C000000000134A38] .reiserfs_check_lock_depth+0x30/0x48
> [C00000076E6939C0] [C00000000013A654] .do_journal_begin_r+0x58/0x434
> [C00000076E693AB0] [C00000000013AC54] .journal_begin+0x108/0x170
> [C00000076E693B50] [C000000000123130] .reiserfs_remount+0x194/0x460
> [C00000076E693C50] [C0000000000B47D0] .do_remount_sb+0x1a8/0x224
> [C00000076E693CF0] [C0000000000D0E98] .sys_umount+0x19c/0x2a0
> [C00000076E693E30] [C00000000000872C] syscall_exit+0x0/0x40

That thump you heard was the sound of
vfs-bkl-is-not-required-for-remount_fs.patch getting dropped.  Thanks.

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