linux-kernel - Re: 2.6.36-rc1 oopses at boot time in kobject allocation

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]

Message-ID: <4C6E799A.7060902@cs.cmu.edu>
Date:	Fri, 20 Aug 2010 08:48:26 -0400
From:	Benjamin Gilbert <bgilbert@...cmu.edu>
To:	Greg KH <gregkh@...e.de>
CC:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.36-rc1 oopses at boot time in kobject allocation

On 08/19/2010 04:34 PM, Greg KH wrote:
> On Thu, Aug 19, 2010 at 04:22:33PM -0400, Benjamin Gilbert wrote:
>> 2.6.36-rc1 and 2.6.36-rc1-127-g763008c fail to boot for me:
> 
> Can you run 'git bisect' to try to track this down?

commit f8a4bd3456b988fc73b2c291b9e01b434c8fa940
Author: Dmitry Torokhov <dmitry.torokhov@...il.com>
Date:   Fri Jun 4 00:54:43 2010 -0700

    firmware loader: embed device into firmware_priv structure
    
    Both these structures have the same lifetime rules so instead of allocating
    and managing them separately embed struct device into struct firmware_priv.
    Also make sure to delete sysfs attributes ourselves instead of expecting
    sysfs to clean up our mess.
    
    Signed-off-by: Dmitry Torokhov <dtor@...l.ru>
    Signed-off-by: Greg Kroah-Hartman <gregkh@...e.de>


Of note, in the original dmesg log, ipw2200 fails to find its firmware
immediately before the backtraces start.  If I build ipw2200 as a module
instead, it finds its firmware and the system boots successfully.

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