Return-path: Received: from h118.nextmail.ru ([194.67.36.118]:39697 "EHLO h118.nextmail.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755502Ab2AIHkR (ORCPT ); Mon, 9 Jan 2012 02:40:17 -0500 To: =?koi8-r?B?TW9oYW1tZWQgU2hhZmk=?= From: =?koi8-r?B?TVI=?= CC: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org, "=?koi8-r?B?UmFqa3VtYXIgTWFub2hhcmFu?=" Subject: =?koi8-r?B?UmU6IGF0aDlrIGNyYXNoIDMuMi1yYzc=?= Date: Mon, 09 Jan 2012 11:40:14 +0400 Message-ID: (sfid-20120109_084022_046513_B9B4DA4D) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-wireless-owner@vger.kernel.org List-ID: >> 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. > > as per our assumption, we should not see those over/underflow errors, > with the patch > above mentioned. please let us know if you hit upon this warnings, > even after the proper fix. In my experience (and as I understand the situation) if garbage is writen to the "chan", it is caught by the check and device is dead-until-reboot anyway. On 3.0, even without checks device was dead-until-reboot, but no crash happened. All these checks do is converting "panic" to "WiFi broken" for 3.2.