netdev - Re: BUG: soft lockup detected on CPU#0! (2.6.18.2 plus hacks)

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: <OFD014A990.71736F9E-ON88257258.0079E460-88257258.007A382C@us.ibm.com>
Date:	Wed, 3 Jan 2007 14:14:58 -0800
From:	David Stevens <dlstevens@...ibm.com>
To:	Ben Greear <greearb@...delatech.com>
Cc:	jarkao2@...pl, NetDev <netdev@...r.kernel.org>
Subject: Re: BUG: soft lockup detected on CPU#0!  (2.6.18.2 plus hacks)

Ben & Jarek,
        Your analysis looks correct to me. It seems to me the problem is 
that
we don't want the in_device to be searchable until after the 
initialization is done.
What about moving the initialization of dev->ip_ptr in inetdev_init() to 
after the
"out" label?

                                                        +-DLS

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html