netdev - Re: BUG: All network processes hang (brcmsmac/wpa

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:	Wed, 19 Oct 2011 15:05:29 +0200
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Arend van Spriel <arend@...adcom.com>
Cc:	Nico Schottelius <nico-linux-20111017@...ottelius.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	netdev <netdev@...r.kernel.org>
Subject: Re: BUG: All network processes hang (brcmsmac/wpa_supplicant)

Le mercredi 19 octobre 2011 à 14:58 +0200, Arend van Spriel a écrit :
> On 10/19/2011 02:49 PM, Eric Dumazet wrote:
> > Le mercredi 19 octobre 2011 à 14:36 +0200, Nico Schottelius a écrit :
> >> Hello,
> >>
> >> I've
> >>
> >> Eric Dumazet [Tue, Oct 18, 2011 at 02:24:25PM +0200]:
> >>> Must be a mutex_unlock(some_mltex) missing somewhere.
> >>>
> >>> Then later, a process holding RTNL is blocking on mutex_lock(some_mutex)
> >>>
> >>> Try a "CONFIG_LOCKDEP=y" enabled build
> >>
> >> Did so, attached is the dmesg output after 3x suspend.
> >>
> >> It also seems this bug gets more / only triggered when I loose the
> >> connection to a wpa2-eap network that is defined like this:
> >>
> >> network={
> >>    ssid="eth"
> >>   id_str="eth-802.2x"
> >>    key_mgmt=WPA-EAP
> >>    proto=WPA2
> >>    eap=TTLS
> >>    pairwise=CCMP TKIP
> >>    group=CCMP TKIP
> >>    phase2="auth=MSCHAPV2"
> >>    identity="MYNAME"
> >>    password="forgottoremoveit"
> >> }
> >>
> >> Hope the dmesg output helps and we can remove the problem soon
> >> and making the mba finally almost completly usable :-)
> >>
> > 
> > Sorry, no CONFIG_LOCKDEP in your config or dmesg. Maybe you sent a
> > previous dmesg/config file ?
> > 
> > Note that you have "CONFIG_LOCKDEP_SUPPORT=y", not "CONFIG_LOCKDEP=y"
> > 
> 
> Hi Eric,
> 
> Are there any configuration setting needed that CONFIG_LOCKDEP depends on?



config LOCKDEP
        bool
        depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
        select STACKTRACE
        select FRAME_POINTER if !MIPS && !PPC && !ARM_UNWIND && !S390 && !MICROBLAZE
        select KALLSYMS
        select KALLSYMS_ALL

make menuconfig
 -> Kernel hacking
   -> Lock debugging: prove locking correctness



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