linux-kernel - Re: pull request: wireless-2.6 2008-11-25

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:	Tue, 25 Nov 2008 14:52:23 -0800
From:	"Luis R. Rodriguez" <lrodriguez@...eros.com>
To:	"John W. Linville" <linville@...driver.com>
CC:	"davem@...emloft.net" <davem@...emloft.net>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	<zenczykowski@...il.com>
Subject: Re: pull request: wireless-2.6 2008-11-25

On Tue, Nov 25, 2008 at 02:08:24PM -0800, John W. Linville wrote:
> Dave,
> 
> These fixes are intended for 2.6.28.  Included are a build fix,
> a security issue (debugfs permissions), a fixup to a previous patch
> from Johannes to correct some DMA API usage, a fix to prevent mac80211
> from allowing the use of IBSS mode on channels that don't allow it,
> an ath5k fix to limit wakeups when not associate, and some ath9k DMA
> fixes for a problem that led to disk corruption...

BTW, just for the record, the culprit to disk corruption on ath9k
seems to be a bug in the swiotlb emergency buffer. If bored please
bugzilla 11811 [1] for more information and also a suggested patch
for how to fix this by Maciej, which he should be sending to
linux-kernel soon hopefully.

The swiotlb issue should not affect us anymore though as we now don't starve
the swiotlb of bounce buffers and hence no reason to rely on the buggy
emergency buffer.

[1] http://bugzilla.kernel.org/show_bug.cgi?id=11811

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