netdev - Re: xen-netback regression in 3.10.18

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: <1384248426.1883.16.camel@kazak.uk.xensource.com>
Date:	Tue, 12 Nov 2013 09:27:06 +0000
From:	Ian Campbell <Ian.Campbell@...rix.com>
To:	David Miller <davem@...emloft.net>
CC:	<david.vrabel@...rix.com>, <netdev@...r.kernel.org>,
	<stable@...r.kernel.org>, <paul.durrant@...rix.com>,
	<wei.liu2@...rix.com>
Subject: Re: xen-netback regression in 3.10.18

On Sat, 2013-11-09 at 15:57 -0500, David Miller wrote:
> From: David Vrabel <david.vrabel@...rix.com>
> Date: Thu, 7 Nov 2013 12:15:33 +0000
> 
> > 3.10.18 included 279f438e36c0 (xen-netback: Don't destroy the netdev
> > until the vif is shut down) but this has a regression that was fixed by
> > dc62ccaccfb1 (xen-netback: transition to CLOSED when removing a VIF)
> > 
> > dc62ccaccfb1 depends on ea732dff5cfa (xen-netback: Handle backend state
> > transitions in a more robust way) which is also a bug fix for certain
> > Windows frontend drivers and is thus also a stable candidate.
> > 
> > Dave can you ensure these two commits are tagged for the next 3.10.y
> > stable release?
> > 
> >   ea732dff5cfa10789007bf4a5b935388a0bb2a8f
> >   dc62ccaccfb139d9b04bbc5a2688a4402adbfab3
> 
> Ian already asked me to do this,

Sorry, bit of a race condition after Dave V and I spoke. Seems like I
won by 3s ;-)

> and the commits are necessary for 3.11 -stable as well.
> 
> They've been queued up.

Thanks.

Ian.


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