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 14:58:49 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Heinz Diehl <htd@...cy-poultry.org>
cc:	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 Mon, 20 Sep 2010, Heinz Diehl wrote:

> On 12.08.2010, Heinz Diehl wrote: 
> 
> > > >>Could please those of you, who are able to reproduce the problem, verify
> > > >>whether the patch below (completely untested) makes everything behave
> > > >>again? Thanks.
>  
> > > >Yes, everything behaves again. Thanks Jiri.
>   
> > > Seconded. Works good. Thanks for your support Jiri.
>  
> > Thirded! This fixes the warning here.
> 
> Unfortunately, I have to take up this problem a second time. 
> I considered the issue fixed, and in fact it was using Jiris patch.
> 
> However, the same problem came back while testing 2.6.36-rc4 and the
> following -git's. /var/log/warn shows the same warning as mentioned in
> the first mail in this thread:
> 
>  Sep 20 08:18:42 liesel apcupsd[5436]: apcupsd FATAL ERROR in linux-usb.c at line 609 
>  Cannot find UPS device -- For a link to detailed USB trouble
>  shooting information, please see <http://www.apcupsd.com/support.html>.
>  Sep 20 08:18:42 liesel apcupsd[5436]: apcupsd error shutdown completed
> 
> No additional oops this time, only the warning, and my UPS is no longer
> working.
> 
> 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.

The error you see must have a different cause.  Have you read this 
thread?

	http://marc.info/?t=128494644600005&r=1&w=2

Alan Stern

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