From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: RFC/PATCH: xen: race during domain destruction [Re: [xen-4.7-testing test] 105948: regressions - FAIL] Date: Sun, 26 Feb 2017 16:53:03 +0100 Message-ID: <1488124383.5548.72.camel@citrix.com> References: <4b6337e3-74b3-8ecd-d7a6-aa8a451fb8d3@citrix.com> <58AD5DDA020000780013C9ED@prv-mh.provo.novell.com> <1487952877.5548.26.camel@citrix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0699103548926232009==" Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ci18N-0000kH-Th for xen-devel@lists.xenproject.org; Sun, 26 Feb 2017 15:53:16 +0000 In-Reply-To: <1487952877.5548.26.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Jan Beulich , Andrew Cooper Cc: George Dunlap , xen-devel , osstest service owner , Juergen Gross List-Id: xen-devel@lists.xenproject.org --===============0699103548926232009== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="=-wivZ3sk+QX1FHwMuRY5/" --=-wivZ3sk+QX1FHwMuRY5/ Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2017-02-24 at 17:14 +0100, Dario Faggioli wrote: > On Wed, 2017-02-22 at 01:46 -0700, Jan Beulich wrote: > > However, comparing with the staging version of the file > > (which is heavily different), the immediate code involved here > > isn't > > all that different, so I wonder whether (a) this is a problem on > > staging too or (b) we're missing another backport. Dario? > >=20 > So, according to my investigation, this is a genuine race. It affects > this branch as well as staging, but it manifests less frequently (or, > I > should say, very rarely) in the latter. >=20 Actually, this is probably wrong. It looks like the following commit: =C2=A0f3d47501db2b7bb8dfd6a3c9710b7aff4b1fc55b =C2=A0xen: fix a (latent) cpupool-related race during domain destroy is not in staging-4.7. At some point, while investigating, I thought I had seen it there, but I was wrong! So, I'd say that the proper solution is to backport that change, and ignore the drafted patch I sent before. In any case, I'll try doing the backport myself and test the result on Monday (tomorrow). And I will let you know. Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-wivZ3sk+QX1FHwMuRY5/ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJYsvnfAAoJEBZCeImluHPuDmQP/3mo8lPxsIybIRAxerC9XZpK sOn7NaP08up4QCW1OelsIptISpumlaAum8xNGAVSwyAjlT6ALIORzE7tX0TcYbPJ H+9xD8Z/fZ90o60xqsfMsK70RL6v4dlkBZ5le16nnv/Ubk6WnaNCbVIHHA2dOEC/ ObpphywuwLsS7N/bXPocode8g2Rj4LNczQVPCColrwBAI3hzVipyjmG0KJ67sph1 PhdicUfYZE6HBlxFpE+zI3ed5xXDjnXdv4i0mNIN8NDUfsnP8HPeNhJsqY3c/2ki OF55E75ykrXx1I1uArDgZxlhEcSZD9R2ZSdzSoBJx63v6EAW1G2sw0s1QoKy8/P2 5tQHGn2lXlwaNgjc5ADSP1PMaFEx2KQ0vtNINGPm8LpwHWnTFG8KxeMP06nFCieY q777wgBWUt24jj24m2NDzc76C+s+tNKpL6SxuQX+qpemBEDO2B1ddmOEwkxi58Z4 Dp1EASHVzGUe+wJ/pO5KNLR192HtwoNyf2qshfB42gXgQxufYd5qAoVCNGQCdf0H jzaFTUamjEd6czBMlfGve0ou7gQ01viMuW/gOY1fsiLlvKV6S+R/9MEd4vMak5Aa SueOJa4Ef1GaQ/RWj03gQ1jJHBuPGPxWxUyIVRhw4TpUlJQCe9sIP1rm1eHyfV9E zva+qJYZ5/DD5rGXk6Ms =Ak6o -----END PGP SIGNATURE----- --=-wivZ3sk+QX1FHwMuRY5/-- --===============0699103548926232009== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --===============0699103548926232009==--