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=-8.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham 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 129F8C433B4 for ; Mon, 19 Apr 2021 07:07:53 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id ADCD661027 for ; Mon, 19 Apr 2021 07:07:52 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org ADCD661027 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:58214 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lYO0d-0004xV-Ps for qemu-devel@archiver.kernel.org; Mon, 19 Apr 2021 03:07:51 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:49794) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lYNyy-0003g3-74 for qemu-devel@nongnu.org; Mon, 19 Apr 2021 03:06:08 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:31729) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lYNys-0000yF-FW for qemu-devel@nongnu.org; Mon, 19 Apr 2021 03:06:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1618815960; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Ih7mqqcs/idY/1fdQqD/7arLltDPgItBZMlPpPhPDvk=; b=bbo7QG9+CtfwGrD8Kee5iNh04yyI5ONjBURWqFa13Ei4Y4TSFWLI2bmA3qAFnGcH6ot+fD 49/cbVSUS3smCWKrT0FZN8UG4rFHgrO1dPt6Y7lP2ij5ls6Q+VQ0WllAL1i8bF4dyhKkzz FMPP2M8WB2KxDd8hWMKYtSN7RkMgyQE= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-573-qI0E4DrYPGmjD2NolMaS1Q-1; Mon, 19 Apr 2021 03:05:57 -0400 X-MC-Unique: qI0E4DrYPGmjD2NolMaS1Q-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 0CD8287A83E; Mon, 19 Apr 2021 07:05:56 +0000 (UTC) Received: from gondolin.fritz.box (ovpn-113-200.ams2.redhat.com [10.36.113.200]) by smtp.corp.redhat.com (Postfix) with ESMTP id 2B2D75C237; Mon, 19 Apr 2021 07:05:53 +0000 (UTC) Date: Mon, 19 Apr 2021 09:05:51 +0200 From: Cornelia Huck To: Mark Cave-Ayland Subject: Re: any remaining for-6.0 issues? Message-ID: <20210419090551.4a3ae4eb.cohuck@redhat.com> In-Reply-To: References: Organization: Red Hat GmbH MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=cohuck@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Received-SPF: pass client-ip=216.205.24.124; envelope-from=cohuck@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Laurent Vivier , Peter Maydell , Thomas Huth , Philippe =?UTF-8?B?TWF0aGlldS1EYXVkw6k=?= , Richard Henderson , QEMU Developers , Alex =?UTF-8?B?QmVu?= =?UTF-8?B?bsOpZQ==?= Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Sun, 18 Apr 2021 11:38:09 +0100 Mark Cave-Ayland wrote: > On 17/04/2021 20:46, Peter Maydell wrote: > > >> On 14/04/2021 13:48, Thomas Huth wrote: > >>> I've seen some intermittend, non-reproducible crashes with usermode QEMU in some of > >>> my CI runs, e.g.: > >>> > >>> https://gitlab.com/thuth/qemu/-/jobs/1178256498#L3876 > >>> > >>> https://gitlab.com/thuth/qemu/-/jobs/1146276208#L3241 > >>> > >>> This was only with ccache enabled, so I thought that it might be related to my > >>> work-in-progress ccache patches... > >>> > >>> ... but now Cornelia reported that she has seen such a crash in one of her branches, > >>> too (which is completely unrelated to my ccache patches): > >>> > >>> https://gitlab.com/cohuck/qemu/-/jobs/1178860927#L3867 > >>> > >>> That makes me wonder whether we currently have a real problem with user-mode in the > >>> master branch? Did anybody else see such problems? > >> > >> I've definitely seen the same issue as Cornelia in my Gitlab CI builds for the ESP > >> security fixes (first version of which appeared just before rc0). The user builds > >> always fail on "run-tcg-tests-s390x-linux-user" for me. > > > > Do we have any better understanding yet of the cause here? > > (I ask because I think we're going to need an rc4 for other reasons, > > so if there's a ready-to-go fix then we could consider it.) > > I don't think so. I tried a run with a possible candidate patch reverted (see > https://lists.gnu.org/archive/html/qemu-devel/2021-04/msg02345.html) but Cornelia's > response indicates that the result is still inconclusive :( That patch seems to be our best candidate so far, but the intermittent nature of the failures make it hard to pin down... I don't see anything obviously wrong with the patch, maybe some linux-user experts have a better idea?