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=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 9EAEDC76191 for ; Thu, 25 Jul 2019 16:46:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 7F7782238C for ; Thu, 25 Jul 2019 16:46:12 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727026AbfGYQqM (ORCPT ); Thu, 25 Jul 2019 12:46:12 -0400 Received: from mga04.intel.com ([192.55.52.120]:33320 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726781AbfGYQqL (ORCPT ); Thu, 25 Jul 2019 12:46:11 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Jul 2019 09:46:11 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,307,1559545200"; d="scan'208";a="171862867" Received: from sjchrist-coffee.jf.intel.com (HELO linux.intel.com) ([10.54.74.165]) by fmsmga007.fm.intel.com with ESMTP; 25 Jul 2019 09:46:11 -0700 Date: Thu, 25 Jul 2019 09:46:11 -0700 From: Sean Christopherson To: Paolo Bonzini Cc: Naresh Kamboju , Greg Kroah-Hartman , Anders Roxell , Ben Hutchings , wanpengli@tencent.com, Linus Torvalds , patches@kernelci.org, Linux Kernel Mailing List , lkft-triage@lists.linaro.org, linux- stable , Andrew Morton , Shuah Khan , Guenter Roeck , jmattson@google.com Subject: Re: [PATCH 5.2 000/413] 5.2.3-stable review Message-ID: <20190725164610.GE18612@linux.intel.com> References: <20190724191735.096702571@linuxfoundation.org> <20190725113437.GA27429@kroah.com> <230a5b34-d23e-8318-0b1f-d23ada7318e0@redhat.com> <20190725160939.GC18612@linux.intel.com> <33f1cfaa-525d-996a-4977-fda32dc368ee@redhat.com> <20190725162053.GD18612@linux.intel.com> <7bc207e0-0812-e41a-bfd5-e3fbfd43f242@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7bc207e0-0812-e41a-bfd5-e3fbfd43f242@redhat.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Thu, Jul 25, 2019 at 06:30:10PM +0200, Paolo Bonzini wrote: > On 25/07/19 18:20, Sean Christopherson wrote: > > On Thu, Jul 25, 2019 at 06:10:37PM +0200, Paolo Bonzini wrote: > >> On 25/07/19 18:09, Sean Christopherson wrote: > >>>> This investigation confirms it is a new test code failure on stable-rc 5.2.3 > >>> No, it only confirms that kvm-unit-tests/master fails on 5.2.*. To confirm > >>> a new failure in 5.2.3 you would need to show a test that passes on 5.2.2 > >>> and fails on 5.2.3. > >> > >> I think he meant "a failure in new test code". :) > > > > Ah, that does appear to be the case. So just to be clear, we're good, right? > > Yes. I'm happy to gather ideas on how to avoid this (i.e. 1) if a > submodule would be useful; 2) where to stick it). As a starting point, what about adding "stable" branches for each kernel release to kvm-unit-tests, e.g. linux-5.2.y? I assume we'd need something similar for the submodules anyways.