linux-kernel - Re: kobject: delayed kobject release: help find buggy drivers

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:	Thu, 5 Sep 2013 17:26:06 -0400
From:	Dave Jones <davej@...hat.com>
To:	Russell King - ARM Linux <linux@....linux.org.uk>,
	Greg KH <gregkh@...uxfoundation.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: kobject: delayed kobject release: help find buggy drivers

On Thu, Sep 05, 2013 at 05:11:13PM -0400, Dave Jones wrote:
 
 >  > Trying without serial console next..
 > 
 > rebuilt with all serial turned off.
 > 
 > no luck, then it oopses somewhere else. I'm suspecting something isn't
 > right with that debug patch, as the next trace is also in kobject_release

I managed to get to userspace on one boot, and got this.

kobject ffff88023d93f518 has been corrupted (magic 0x6b6b6b6b).  Please enable kobject debugging for full debug.

That looks like SLAB_POISON. Incompatibility between the two options ?

For some reason, even though I have DEBUG_KOBJECT on, I didn't get extra messages output.

	Dave

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