linux-kernel - Re: ath9k crash 3.2-rc7

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:	Mon, 09 Jan 2012 11:05:23 +0400
From:	MR <g7af0ec1e3ea1e7b1@...tmail.ru>
To:	Mohammed Shafi <shafi.wireless@...il.com>
CC:	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
	"Rajkumar Manoharan" <rmanohar@....qualcomm.com>
Subject: Re: ath9k crash 3.2-rc7

 > > Around 23 hours have elapsed.
 > >
 >> WiFi seems to be working 100% of time. It is always at least lightly
 >loaded.

45h - all OK.

 > great and thanks a lot for testing!

Doesn't really require _doing_ anything except building patched kernels. And 
it is in my best interest to test the driver for the WiFi card I use...

 > rather than removing the suspicious code
 > this is properly fixed by us with this patch.
 > http://marc.info/?l=linux-wireless&m=132595161516806&w=2

Ah, I saw the message and wondered whether it is the fix I needed and what 
patches should I apply.

So, I am building 3.2 with two patches: over/under-flow catcher (pity that 
it seems to be on a multiple-times-per-second codepath and just leaving the 
checks there for everyone is suboptimal) and allegedely proper fix. Both 
applied OK with a small offset.

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