netdev - Re: [PATCH 01/34]bnx2x: Using singlethread work queue

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: <20090114.212302.80063588.davem@davemloft.net>
Date:	Wed, 14 Jan 2009 21:23:02 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	eilong@...adcom.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH 01/34]bnx2x: Using singlethread work queue

From: "Eilon Greenstein" <eilong@...adcom.com>
Date: Wed, 14 Jan 2009 18:42:40 +0200

> Since slow-path events, including link update, are handled in
> work-queue, a race condition was introduced in the self-test that
> sometimes caused the link status to fail: the self-test was running
> under RTNL lock, and if the link-watch was scheduled it stoped the
> shared work-queue (waiting for the RTNL lock) and so the link update
> event was not handled until the self-test ended (releasing the RTNL
> lock) with failure (since the link status was not updated)
>
> Signed-off-by: Eilon Greenstein <eilong@...adcom.com>

Applied.
--
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