linux-kernel - Re: [origin tree SLAB corruption #2] BUG kmalloc-64: Poison overwritten, INFO: Allocated in bdi_alloc

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: <20090915074802.GA21895@elte.hu>
Date:	Tue, 15 Sep 2009 09:48:02 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Eric Paris <eparis@...hat.com>,
	Pekka Enberg <penberg@...helsinki.fi>,
	James Morris <jmorris@...ei.org>, Thomas Liu <tliu@...hat.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [origin tree SLAB corruption #2] BUG kmalloc-64: Poison
	overwritten, INFO: Allocated in bdi_alloc_work+0x2b/0x100 age=175
	cpu=1 pid=3514


* Ingo Molnar <mingo@...e.hu> wrote:

> > trying to pull in:
> > 
> >   git://git.kernel.dk/linux-2.6-block.git writeback
> > 
> > and see if it reproduces there? That path has been cleaned up 
> > considerably there.
> 
> I gave it a test-pull - and the bug does not trigger anymore.
> 
> Note, that may not mean much: your tree is based on a fresh upstream 
> tree so it pulled a lot of new stuff into -tip that i have yet to 
> test/validate. It also changed the kernel image size/layout 
> considerably and this bug seems to be a very narrow to hit race of 
> sorts.

Btw., is there anything in your cleanups that could explain this bug? 
Some list handling bug? A double free? Uninitialized memory? Race 
between block IRQs and process context?

	Ingo
--
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/