linux-kernel - Re: [PATCH -net-next 3/4] firmware: convert tg3 driver to request

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]

Message-ID: <496211F3.3000003@hartkopp.net>
Date:	Mon, 05 Jan 2009 14:58:11 +0100
From:	Oliver Hartkopp <oliver@...tkopp.net>
To:	Jaswinder Singh Rajput <jaswinder@...radead.org>
CC:	davem@...hat.com, jgarzik@...hat.com,
	netdev <netdev@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>, linux-next@...r.kernel.org,
	mchan@...adcom.com
Subject: Re: [PATCH -net-next 3/4] firmware: convert tg3 driver to request_firmware()

Oliver Hartkopp wrote:
>  
>
> 2. I got this inconsistent lock state, i've not seen before:
>

Hm - that was not completely correct 8->

I found some more of these lock state issues in my /var/log/kern.log but 
all of them are in the tg3 receive path ... (attached).

So this problem seems not to come from your request_firmware() 
conversion. Maybe there was some other change in the 2.6.28-git that 
causes these tg3 problems.

Regards,
Oliver





View attachment "tg3lockstate1" of type "text/plain" (6316 bytes)

View attachment "tg3lockstate2" of type "text/plain" (6315 bytes)