linux-kernel - Re: kobject (ffff88003ffbb4b8): tried to init an initialized object, something is seriously wrong.

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:	Fri, 3 Feb 2012 13:39:49 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: kobject (ffff88003ffbb4b8): tried to init an initialized object,
 something is seriously wrong.

On Fri, Feb 03, 2012 at 03:59:53PM -0500, Konrad Rzeszutek Wilk wrote:
> Hey Greg,
> 
> With or without your previous patch (the one that added an cpu_device_release
> function) I am getting this in 3.3-rc2.  I did not get this in 3.2.
> 
> I added some extra printks to make sure that the handle_vcpu_hotplug_event
> code actually did call 'arch_unregister_cpu' which is certainly looks
> to be doing.
> 
> I hadn't done a bisection yet, but was wondering if this is related
> to the previous issues with the sysdev. Or kobject getting more observant.

No, it's related to the previous issue, let me knock up a patch to fix
this as well...

thanks,

greg k-h
--
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/