Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755258AbdDDSAh (ORCPT ); Tue, 4 Apr 2017 14:00:37 -0400 Received: from mx1.redhat.com ([209.132.183.28]:51924 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754524AbdDDSAf (ORCPT ); Tue, 4 Apr 2017 14:00:35 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com C4F5880F8E Authentication-Results: ext-mx03.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx03.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=mst@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com C4F5880F8E Date: Tue, 4 Apr 2017 21:00:31 +0300 From: "Michael S. Tsirkin" To: Mike Galbraith Cc: Christoph Hellwig , Thorsten Leemhuis , virtio-dev@lists.oasis-open.org, Linux Kernel Mailing List , rjones@redhat.com Subject: Re: Random guest crashes since 5c34d002dcc7 ("virtio_pci: use shared interrupts for virtqueues") Message-ID: <20170404205921-mutt-send-email-mst@kernel.org> References: <20170331194416-mutt-send-email-mst@kernel.org> <20170403141823.GA24747@lst.de> <1491242192.5638.111.camel@gmx.de> <20170403210931-mutt-send-email-mst@kernel.org> <1491278572.5198.28.camel@gmx.de> <20170404163725-mutt-send-email-mst@kernel.org> <1491315482.5239.11.camel@gmx.de> <20170404182904-mutt-send-email-mst@kernel.org> <1491327646.4253.2.camel@gmx.de> <1491328476.4253.10.camel@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1491328476.4253.10.camel@gmx.de> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Tue, 04 Apr 2017 18:00:35 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1526 Lines: 45 On Tue, Apr 04, 2017 at 07:54:36PM +0200, Mike Galbraith wrote: > On Tue, 2017-04-04 at 19:40 +0200, Mike Galbraith wrote: > > On Tue, 2017-04-04 at 18:30 +0300, Michael S. Tsirkin wrote: > > > > > I couldn't reproduce it - let's make sure we are using the > > > same tree. Could you pls try > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux > > > -next > > > > > > It's currently at cc79d42a7d7e57ff64f406a1fd3740afebac0b44 > > > > Things that make ya go hmm... > > Making double sure we're on the same page... > > git@homer:..git/vhost> git branch > * linux-next > master > git@homer:..git/vhost> git describe > warning: tag 'for_linus' is really 'tags_for_linus' here > for_linus-220128-gcc79d42a7d7e > git@homer:..git/vhost> git status > On branch linux-next > Your branch is up-to-date with 'origin/linux-next'. > Changes not staged for commit: > (use "git add ..." to update what will be committed) > (use "git checkout -- ..." to discard changes in working directory) > > modified: Makefile > modified: scripts/setlocalversion > > no changes added to commit (use "git add" and/or "git commit -a") > git@homer:..git/vhost> > > Modifications are me whacking '+' sign and -rc5.. I don't do those. And just making double sure, the 1st version that has the issue is 5c34d002dcc7, isn't it? I'm asking because subject says so but then goes on to list subject from another commit. This one is: virtio_pci: remove struct virtio_pci_vq_info -- MST