Xen project Mailing List

Re: [linux-linus test] 171361: regressions - FAIL

Date: Mon, 27 Jun 2022 09:38:02 +0200

Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=suse.com; dmarc=pass action=none header.from=suse.com; dkim=pass header.d=suse.com; arc=none

Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=8R2xoE4z7WlDdFZ7FALH/2LOEwGBJ+De5YfxWiGdGDw=; b=TQQX6nNaZXL9+/6+4lDqB1DuC7kBn2xaO03W14xLH0bHYyCiTdJQWPchQKHPboYrp0IxF992i/wr53BUnr5WcYfg6IK4bpEUWdiv+QNdPdJdUoOLrIV32XSC2Gioeb5W4LHKkJdJmG0YGMHpYAXDgNhB2UVwk0wIyY7Hy9jUBxAoxofOVNIiWLlq0FkgxG49RpXPKIL/jhmLSs1c2ccsVYGwLqoJpU5XtCbmR+ICgyCe6ULTOF/JVKGR8rUryh9A4ekmZ6CDBgxq63EBy2GmGVrIAa9YoARmdlK8N+X+BtLZy3gluNnoQ+USvcplQQaC7JojMA1mkS9B640x07bP9A==

Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=j0SZqU2QbQ/1bAy8fCRJI+Vcpe2VnOwb0LGdLsjem2DE7lYgCr3lAU1YFgJj69pE7C4tjEtJ6l2mAW+7NquqeixLMYTZ/rhaYXkhGHNlWJhcsy5+Bs5RfUdIjoMS7OaWhs+hOvOCOKK4oVs0NUqyyJIWujmjerE/mjQv2/ZIxDdV76oDydhOoRIvk5jk5CAor5TXA/OGIbZWhFQ4Hq3uMBWmO7ll06yAx2bLNyb+7uYFsHokMmfgs8MRoE4j0nT89ZHY0C3iOe5nVJ1VR9E7K67GfOn7YFBTlczldkfCFZ+PTyymf76ipaGyaZ8hlGsxmkQELFVQ/5veSEQKZRFukA==

Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=suse.com;

Cc: osstest service owner <osstest-admin@xxxxxxxxxxxxxx>

Delivery-date: Mon, 27 Jun 2022 07:38:12 +0000

List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 27.06.2022 03:38, osstest service owner wrote: > flight 171361 linux-linus real [real] > http://logs.test-lab.xenproject.org/osstest/logs/171361/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > test-amd64-amd64-dom0pvh-xl-intel 8 xen-boot fail REGR. vs. > 171277 > test-amd64-amd64-xl-qemuu-ws16-amd64 8 xen-boot fail REGR. vs. > 171277 > test-amd64-amd64-xl-qemut-win7-amd64 8 xen-boot fail REGR. vs. > 171277 > test-amd64-amd64-pygrub 8 xen-boot fail REGR. vs. > 171277 > test-amd64-amd64-freebsd11-amd64 8 xen-boot fail REGR. vs. > 171277 > test-amd64-amd64-dom0pvh-xl-amd 8 xen-boot fail REGR. vs. > 171277 > test-amd64-amd64-qemuu-nested-amd 8 xen-boot fail REGR. vs. > 171277 > test-amd64-amd64-xl-qemuu-win7-amd64 8 xen-boot fail REGR. vs. > 171277 > test-amd64-amd64-xl-qemut-ws16-amd64 8 xen-boot fail REGR. vs. > 171277 > test-amd64-amd64-xl-qemut-debianhvm-i386-xsm 8 xen-boot fail REGR. vs. > 171277 > test-amd64-amd64-xl-qemuu-debianhvm-i386-xsm 8 xen-boot fail REGR. vs. > 171277 > test-amd64-amd64-xl-qemuu-ovmf-amd64 8 xen-boot fail REGR. vs. > 171277 > test-amd64-amd64-xl-xsm 8 xen-boot fail REGR. vs. > 171277 > test-amd64-amd64-xl 8 xen-boot fail REGR. vs. > 171277 At the example of this: Jun 26 21:51:47.667404 mapping kernel into physical memory Jun 26 21:51:47.667425 about to get started... Jun 26 21:51:47.667435 (XEN) arch/x86/mm.c:2159:d0v0 Bad L1 flags 400000 Jun 26 21:51:47.667448 (XEN) Hardware Dom0 halted: halting machine This is an attempt to install (modify?) a PTE with _PAGE_GNTTAB set via normal page table management hypercalls. Considering how early in the boot process this appears to be, I wonder whether a flag was introduced in the kernel which aliases _PAGE_GNTTAB (or a use of such a pre-existing flag on a path which previously was safe from being hit when running in PV mode under Xen). I wonder if the bisector is already having a go at isolating the offending commit, or whether it had already failed in trying to. Jan

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.