linux-kernel - ath5k deadlock w/ blob transfer

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-next>] [day] [month] [year] [list]

Date:	Fri, 7 May 2010 12:50:59 +0200
From:	Nils Radtke <lkml@...nk-Future.de>
To:	linux-wireless@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org
Subject: ath5k deadlock w/ blob transfer

  Hi,

  Guess, this is better suited in here:

>   - ath5k: when starting a blob transfer eg. ssh summer.jpg to the
>     notebook with the ath5k driver running, the wNIC freezes almost
>     immediately! Dead device. This is unfortunately too easily reproducible.
>     In fact, this is a blocker, wireless blob transfer via ssh (other means
>     not tested) is not possible w/o locking it up.

But wait! I just remembered another case. Using the (incomprehensibly) "obsolete"
madwifi diver (note aside: this driver _does_ reduce the _felt_ deadlock frequency 
or kernel panics, referenced by http://lkml.org/lkml/2010/5/3/229, but not 
entirely make them go away). It evenly locks the wireless NIC while transferring
blobs. 

So where should I be posting this? When both drivers deadlock it's either a common 
base in the wireless driver premisses or yet up the path somewhere in the kernel code.

Ideas?

  Thanks,

    Nils

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