From nobody Fri Jul 07 13:50:37 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QyFCh1JWFz4lCZP; Fri, 7 Jul 2023 13:50:40 +0000 (UTC) (envelope-from mike@karels.net) Received: from mail2.karels.net (mail2.karels.net [3.19.118.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "freebsd", Issuer "freebsd" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QyFCh0v7Rz3mF5; Fri, 7 Jul 2023 13:50:40 +0000 (UTC) (envelope-from mike@karels.net) Authentication-Results: mx1.freebsd.org; none Received: from mail2.karels.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by mail2.karels.net (8.17.1/8.17.1) with ESMTP id 367DocVm026522; Fri, 7 Jul 2023 08:50:38 -0500 (CDT) (envelope-from mike@karels.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=karels.net; s=mail2; t=1688737838; bh=Aq0vIVdB2n8ZnaXzpZ8MW+Ab3yYy6dG3VJw+VV3iGxI=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=cv88D1ylTnbR0Z4BYKeuDsVjI5EjPLLSrlXXVnOcVKxqrNYZnRIeUSPEvZuAQi42U GV30O5lg0KCo0mz2FZnehiLamqMYug5YKFG/1itnkBkJtiGBWdTJ7zY3sh59XJkNk4 e0edl67rBFrIPXEByhv9BI48G3tmk+FtlVyPpNvc7VkdEpab9sgA3FHqZ07OHhE7lC 1sjdbHwtnWXdkJnCXV4x//Wj5S0COL0B0uZVzrph/+HXs/GKdZ2NvcXqIl1baMs+Ht GzkOB1xtQIaXyriowX9XlpTQYV7IOQPs+Fobo8rUdQe3ScUHPJOrco/Nvlkh4uRdG1 L0MSZCDmTNUBg== Received: from [10.0.2.130] ([73.62.165.147]) by mail2.karels.net with ESMTPSA id CsA4Ii4YqGSYZwAAs/W3XQ (envelope-from ); Fri, 07 Jul 2023 08:50:38 -0500 From: Mike Karels To: John F Carr Cc: Current FreeBSD , Mark Millard , freebsd-arm Subject: Re: For snapshot builds: armv7 chroot on aarch64 has kyua test -k /usr/tests/Kyuafile sys/kern/kern_copyin hung up [in getpid?], unkillable, prevents reboot Date: Fri, 07 Jul 2023 08:50:37 -0500 X-Mailer: MailMate (1.14r5964) Message-ID: <106875C8-76F9-4307-A495-D41EAE8F1C8B@karels.net> In-Reply-To: <240A32EC-E255-4B04-83B3-0D57308B701B@mit.edu> References: <7A41DED4-876F-4270-A980-549A4832B39A.ref@yahoo.com> <7A41DED4-876F-4270-A980-549A4832B39A@yahoo.com> <3404EA26-BFDD-4B87-830B-62CB6E91C0BD@karels.net> <240A32EC-E255-4B04-83B3-0D57308B701B@mit.edu> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4QyFCh0v7Rz3mF5 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16509, ipnet:3.16.0.0/14, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 7 Jul 2023, at 6:06, John F Carr wrote: > On Jul 6, 2023, at 20:42, Mike Karels wrote: >> >> >> Thanks for isolating this. Let me know when you have the bug number. >> I just tested a fix (the compat code drops the reference on the curren= t >> address space an extra time, probably freeing it). >> >> Mike The fix is in https://cgit.freebsd.org/src/commit/?id=3Dbe30fd3ab2e8418a6= 96e69f54a91a7e2db5962de. > The bug was introduced in January, 2022. It allows 32 bit binaries to= crash a 64 bit system when COMPAT_FREEBSD32 is on. Test coverage of the= buggy function (sysctl_kern_proc_vm_layout) was added at the same time. > > There should be routine runs of 32 bit test suites on 64 bit systems. = Although i386 and armv7 are tier 2 systems, the tier 1 COMPAT_FREEBSD32 k= ernel code needs to be exercised. This bug was only discovered by manual= ly running tests in the right environment, 17 months after automated test= ing could have discovered it. That is not so simple currently, as the shared libraries for the test environment are not part of 32-bit compatibility package. The required bits could be extracted from the corresponding 32-bit build, but that isn't easy to automate. Fortunately, I think that very few of the tests exercise any 32-bit-specific code paths. Mike