linux-kernel - Re: 2.6.33-rc0: reiserfs: inconsistent lock state

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]

Message-ID: <20091228171733.GA5014@nowhere>
Date:	Mon, 28 Dec 2009 18:17:37 +0100
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Alexander Beregalov <a.beregalov@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.33-rc0: reiserfs: inconsistent lock state

On Sun, Dec 20, 2009 at 03:09:33PM +0300, Alexander Beregalov wrote:
> Hi Frederic
> 
> This is Linus's v2.6.33-rc1-96-gdd59f6c
> plus your 47376ceba5 "reiserfs: Fix reiserfs lock <-> inode mutex
> dependency inversion"
> 
> [ INFO: inconsistent lock state ]
> 2.6.33-rc1-00101-g476ef56 #1
> ---------------------------------
> inconsistent {RECLAIM_FS-ON-W} -> {IN-RECLAIM_FS-W} usage.
> kswapd0/313 [HC0[0]:SC0[0]:HE1:SE1] takes:
>  (&REISERFS_SB(s)->lock){+.+.?.}, at: [<c1111048>]
> reiserfs_write_lock_once+0x28/0x50
> {RECLAIM_FS-ON-W} state was registered at:
>   [<c104e522>] mark_held_locks+0x62/0x90
>   [<c104e5ea>] lockdep_trace_alloc+0x9a/0xc0
>   [<c108efa6>] kmem_cache_alloc+0x26/0xf0
>   [<c1085a0c>] __get_vm_area_node+0x6c/0xf0
>   [<c10860fe>] __vmalloc_node+0x7e/0xa0
>   [<c108629b>] vmalloc+0x2b/0x30
>   [<c110d4ba>] journal_init+0x2a/0x9f0



Oh right, I fixed a vmalloc under reiserfs lock
in the mount path but there are some others remaining.

Will fix, 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/