linux-kernel - Re: iwlagn driver segfault in 2.6.28-rc3

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 19 Nov 2008 23:29:40 +0100
From:	"Carlos R. Mafra" <crmafra2@...il.com>
To:	Tomas Winkler <tomasw@...il.com>
Cc:	reinette chatre <reinette.chatre@...el.com>,
	Lukas Hejtmanek <xhejtman@....muni.cz>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"ipw3945-devel@...ts.sourceforge.net" 
	<ipw3945-devel@...ts.sourceforge.net>
Subject: Re: iwlagn driver segfault in 2.6.28-rc3

On Thu 20.Nov'08 at  0:06:05 +0200, Tomas Winkler wrote:
> >
> > I don't if the situation leading to the WARN() in your patch is the same
> > one which used to kill my wireless connection before (with the oops
> > in iwl_eeprom_query16 that started this thread), but the fact is
> > that my wifi is still working.
> 
> The second removal of invalid key corrupt the eeprom pointer
> in this line
> 
>       if (!test_and_clear_bit(priv->stations[sta_id].sta.key.key_offset,
>                  &priv->ucode_key_table))
> 
> as discovered by Yi so this patch also fix the immediate failure
> We are just not sure in what flow the key is removed second time and maybe
> there is an other issue behind it.

Ok, thanks for the explanation!

> The full log will be appreciated  but you've already helped a lot
> Thanks for your time

I thank you too for taking care of it, and now at least my wifi does not
die as before.

I uploaded the dmesg here

http://www.aei.mpg.de/~crmafra/dmesg-iwlwifi.txt

it contains the warnings including the first (not tainted), 
but the beginning of the log is missing because it was too big I guess.

But the boot messages are probably the same as the other dmesg
I've sent already in this thread.


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