linux-kernel - Re: [BUG] object: is not initialized, yet kobject

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:	Mon, 20 Sep 2010 21:39:13 +0200
From:	Heinz Diehl <htd@...tha.org>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	Heinz Diehl <htd@...cy-poultry.org>, Alan Ott <alan@...nal11.us>,
	Markus Trippelsdorf <markus@...ppelsdorf.de>,
	Jiri Kosina <jkosina@...e.cz>, linux-kernel@...r.kernel.org,
	linux-usb@...r.kernel.org, linux-input@...r.kernel.org,
	Arnd Bergmann <arnd@...db.de>
Subject: Re: [BUG] object: is not initialized, yet kobject_put() is being
 called

On 20.09.2010, Alan Stern wrote: 

> > Jiris patch obviously didn't made it into 2.6.36-rc4, and it doesn't
> > apply nay longer either.
 
> No, you're wrong.  The patch _is_ in 2.6.36-rc4, and that's the reason 
> why it doesn't apply any longer.

Yes, you're right. 

> The error you see must have a different cause.  Have you read this 
> thread?
> 
> 	http://marc.info/?t=128494644600005&r=1&w=2

No, not before until now. This problem seems not to be related to what I 
see on my machines, and reverting commit 8fe294caf8c868edd9046251824a0af91991bf43 as
mentioned in there doesn't help either.

2.6.35.4 works, 2.6.36-rc4 does not. What can I do to help to find the
issue?

Attached are the dmesg output for both 2.6.35.4 and 2.6.36-rc4.



Download attachment "dmesg-2.6.35.4.txt.bz2" of type "application/octet-stream" (12833 bytes)

Download attachment "dmesg-2.6.36-rc4.txt.bz2" of type "application/octet-stream" (12568 bytes)