linux-kernel - Re: pull request: wireless-2.6 2009-05-20

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

Message-Id: <20090520.173408.126761158.davem@davemloft.net>
Date:	Wed, 20 May 2009 17:34:08 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	linville@...driver.com
Cc:	linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: pull request: wireless-2.6 2009-05-20

From: "John W. Linville" <linville@...driver.com>
Date: Wed, 20 May 2009 15:34:47 -0400

> Another volley of fixes intended for 2.6.30 -- I know the velocity
> is a bit high for this part of the cycle, but these are mostly small
> and well-tested.
> 
> The one from me is a "brown paper bag" fix.  My earlier attempt to fix
> the potential buffer overflow in airo was actually a no-op due to an
> (unknown to me) type overflow... :-(
> 
> The ath5k fixes from Forrest Zhang and Pavel Roskin together fix some
> regressions with 5GHz operation.  The one from Fabio Rossi avoids an
> infinite loop reported by Stephen Rostedt.
> 
> The wext fix addresses a possible buffer overflow.  The cfg80211 fix
> addresses a user-reported oops.  The one from Roel avoids and index
> past the end of an array.
> 
> One of iwlwifi patches avoids a deadlock.  The other iwlwifi patch
> simply enables the use of the firmware image they just released.
> That one is worth taking for 2.6.30 because the new firmware fixes
> a couple of bugs that show-up as kernel bug reports.
> 
> Please let me know if there are problems!

Pulled, thanks John!
--
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/