linux-kernel - Re: ath9k becon loss messages

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, 07 Apr 2009 08:54:35 +0300
From:	Kalle Valo <kalle.valo@....fi>
To:	"John W. Linville" <linville@...driver.com>
Cc:	Michael Buesch <mb@...sch.de>,
	Jaswinder Singh Rajput <jaswinder@...nel.org>,
	Sujith <Sujith.Manoharan@...eros.com>,
	wireless <linux-wireless@...r.kernel.org>,
	David Miller <davem@...emloft.net>,
	LKML <linux-kernel@...r.kernel.org>,
	Helmut Schaa <helmut.schaa@...glemail.com>
Subject: Re: ath9k becon loss messages

"John W. Linville" <linville@...driver.com> writes:

> On Mon, Apr 06, 2009 at 06:18:56PM +0300, Kalle Valo wrote:
>
>> When I'm able to implement the proper fix, I think it should first have
>> proper testing in wireles-testing before pushing it to mainline. So
>> maybe the proper fix is 2.6.31 material, just to be on the safe side
>> here.
>> 
>> John, what do you think?
>
> It depends on what the proper fix looks like, but basically anything
> posted in the last week and thereafter is already 2.6.31 material
> unless it is a specific bug fix for what is already in Linus' kernel.

Ok, that settles it then. Because this bug has been in mac80211 for ages
we can wait for 2.6.31.

But do you take Michael's patch[1] for disabling the "beacon loss"
message for 2.6.30? I think we should have it in 2.6.30, otherwise we
will get quite a lot of bug reports. Do you want me to resend it?

[1] http://marc.info/?l=linux-kernel&m=123892431619630&w=2

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