netdev - Re: [PATCHv1 net] xen-netback: release pending index before pushing Tx responses

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: <20150224.162443.2047866685711544650.davem@davemloft.net>
Date:	Tue, 24 Feb 2015 16:24:43 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	david.vrabel@...rix.com
Cc:	netdev@...r.kernel.org, xen-devel@...ts.xenproject.org,
	ian.campbell@...rix.com, wei.liu2@...rix.com
Subject: Re: [PATCHv1 net] xen-netback: release pending index before
 pushing Tx responses

From: David Vrabel <david.vrabel@...rix.com>
Date: Tue, 24 Feb 2015 11:17:59 +0000

> If the pending indexes are released /after/ pushing the Tx response
> then a stale pending index may be used if a new Tx request is
> immediately pushed by the frontend.  The may cause various WARNINGs or
> BUGs if the stale pending index is actually still in use.
> 
> Fix this by releasing the pending index before pushing the Tx
> response.
> 
> The full barrier for the pending ring update is not required since the
> the Tx response push already has a suitable write barrier.
> 
> Signed-off-by: David Vrabel <david.vrabel@...rix.com>

Applied, thanks David.
--
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