Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935141AbdCWN5y convert rfc822-to-8bit (ORCPT ); Thu, 23 Mar 2017 09:57:54 -0400 Received: from prv-mh.provo.novell.com ([137.65.248.74]:57183 "EHLO prv-mh.provo.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932592AbdCWN5w (ORCPT ); Thu, 23 Mar 2017 09:57:52 -0400 X-Greylist: delayed 1210 seconds by postgrey-1.27 at vger.kernel.org; Thu, 23 Mar 2017 09:57:52 EDT Message-Id: <58D3DDB40200007800146C6B@prv-mh.provo.novell.com> X-Mailer: Novell GroupWise Internet Agent 14.2.1 Date: Thu, 23 Mar 2017 07:37:40 -0600 From: "Jan Beulich" To: "Juergen Gross" Cc: , , , , , Subject: Re: [Xen-devel] [PATCH] xen, fbfront: fix connecting to backend References: <20170323125252.11763-1-jgross@suse.com> In-Reply-To: <20170323125252.11763-1-jgross@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 426 Lines: 11 >>> On 23.03.17 at 13:52, wrote: > Connecting to the backend isn't working reliably in xen-fbfront: in > case XenbusStateInitWait of the backend has been missed the backend > transition to XenbusStateConnected will trigger the connected state > only without doing the actions required when the backend has > connected. Looks like xen-kbdfront does exactly the same - shouldn't it also be changed then? Jan