From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 519D2C3F68F for ; Thu, 6 Feb 2020 22:17:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 26A7A21927 for ; Thu, 6 Feb 2020 22:17:29 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="Bs9Lz2p+" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727441AbgBFWR2 (ORCPT ); Thu, 6 Feb 2020 17:17:28 -0500 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:36016 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727443AbgBFWR2 (ORCPT ); Thu, 6 Feb 2020 17:17:28 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1581027447; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=dliw2RAM/nP3vDLbquqsu5FLbVnJwrHBsnpHt8MF4Y8=; b=Bs9Lz2p+ZXJ0cJFtnPu/BAAhMbvh+j1yvWg144fj50x5xlkBdyoBEr2x8q1HVxOJK2QHhl 29l4blarwSvcj4vjMulxcihFrrX0oAMlPtF40SASaP5nrL9Ejfry5jZl0q0rQqEJfXqhla jc8TW2xr73wHMEjOjScOc/uan276LJQ= Received: from mail-qv1-f69.google.com (mail-qv1-f69.google.com [209.85.219.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-295-1c6ft0thN1ODtMveAnLwlw-1; Thu, 06 Feb 2020 17:17:25 -0500 X-MC-Unique: 1c6ft0thN1ODtMveAnLwlw-1 Received: by mail-qv1-f69.google.com with SMTP id c1so4631931qvw.17 for ; Thu, 06 Feb 2020 14:17:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=dliw2RAM/nP3vDLbquqsu5FLbVnJwrHBsnpHt8MF4Y8=; b=QWuQPFSKjYsQYJ2i4efUMbV9sJ9ax5wVJ3JqqumExWCjIVIbZiMf90DCSeTIfVb7S6 Ke3KTNrsuOLXksBvrLMVfT3Ynut0IJ+ABkLLsFOG9HKApp3E+mzHXFeuou9p3yTt/9vZ cIOv+gg7vmAEAzPKabp1Kbw1Gbp267LDmILEEiD4WBblfb6aIFjdr5stmVBWPQD7NLe7 PxFkzzAPhV/iB+dfXyrDF3A7ElfdwmvlHk8nIl62mYdQhz5FuCpIKak9asmDvE2WsOQI x6VomGOX9AYYpRMO825oaGMrjCpQHu8913Kz+NR521NblsvDtJ8n4wnYA0XGDRZ7cUZV Tjbw== X-Gm-Message-State: APjAAAWRyoQQd0dKhSXh3rhWHt6X23bg0GWKXD0bAXSKz9ySCQC+ejlm duSfq6Y9tKpp8ToXgQV0UR3Iu2gIJozRTWSgegQD/66paOJY5mHpAEScAMTDW8ZFDI3VFS6G19v QUx4zgWqTOuKE+HUrYGExNw== X-Received: by 2002:ad4:4c42:: with SMTP id cs2mr4304146qvb.198.1581027445020; Thu, 06 Feb 2020 14:17:25 -0800 (PST) X-Google-Smtp-Source: APXvYqx4aT6nHPT/UCOxB/dIpvh77YFb+ccbCujxO7QlHqlvH0kWVJQHP+Kls/zNpxqC5KRYicsxvQ== X-Received: by 2002:ad4:4c42:: with SMTP id cs2mr4304120qvb.198.1581027444763; Thu, 06 Feb 2020 14:17:24 -0800 (PST) Received: from redhat.com (bzq-79-176-41-183.red.bezeqint.net. [79.176.41.183]) by smtp.gmail.com with ESMTPSA id s22sm362089qke.19.2020.02.06.14.17.21 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 06 Feb 2020 14:17:23 -0800 (PST) Date: Thu, 6 Feb 2020 17:17:19 -0500 From: "Michael S. Tsirkin" To: Christian Borntraeger Cc: eperezma@redhat.com, "virtualization@lists.linux-foundation.org" , Stephen Rothwell , Linux Next Mailing List , "linux-kernel@vger.kernel.org" , kvm list , Halil Pasic Subject: Re: vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot Message-ID: <20200206171349-mutt-send-email-mst@kernel.org> References: <20200106054041-mutt-send-email-mst@kernel.org> <08ae8d28-3d8c-04e8-bdeb-0117d06c6dc7@de.ibm.com> <20200107042401-mutt-send-email-mst@kernel.org> <20200107065434-mutt-send-email-mst@kernel.org> <20200120012724-mutt-send-email-mst@kernel.org> <2a63b15f-8cf5-5868-550c-42e2cfd92c60@de.ibm.com> <1ade56b5-083f-bb6f-d3e0-3ddcf78f4d26@de.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1ade56b5-083f-bb6f-d3e0-3ddcf78f4d26@de.ibm.com> Sender: linux-next-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On Thu, Feb 06, 2020 at 04:12:21PM +0100, Christian Borntraeger wrote: > > > On 06.02.20 15:22, eperezma@redhat.com wrote: > > Hi Christian. > > > > Could you try this patch on top of ("38ced0208491 vhost: use batched version by default")? > > > > It will not solve your first random crash but it should help with the lost of network connectivity. > > > > Please let me know how does it goes. > > > 38ced0208491 + this seem to be ok. > > Not sure if you can make out anything of this (and the previous git bisect log) Yes it does - that this is just bad split-up of patches, and there's still a real bug that caused worse crashes :) So I just pushed batch-v4. I expect that will fail, and bisect to give us vhost: batching fetches Can you try that please?