netdev - RE: [PATCH net-next] bnx2x: Resolving a possible dead-lock situation

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: <1290531342.3046.115.camel@edumazet-laptop>
Date:	Tue, 23 Nov 2010 17:55:42 +0100
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Vladislav Zolotarov <vladz@...adcom.com>
Cc:	Dave Miller <davem@...emloft.net>,
	Eilon Greenstein <eilong@...adcom.com>,
	netdev list <netdev@...r.kernel.org>
Subject: RE: [PATCH net-next] bnx2x: Resolving a possible dead-lock
 situation

Le mardi 23 novembre 2010 à 08:36 -0800, Vladislav Zolotarov a écrit :
> > 
> > That seems strange. Even if performance penalty is not minimal, it
> > should be avoided.
> > 
> > If problem comes from ethtool, why not preventing BH in ethtool itself
> > ?
> 
> Looks good. Let me run a few checks before u submit a patch to Dave. Or do u prefer 
> me to push it on your behalf?

I was only suggesting an alternate patch, I am not able to test it ;)



--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html