From owner-freebsd-stable@freebsd.org Fri Jul 14 00:25:00 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8CDE5DB180D for ; Fri, 14 Jul 2017 00:25:00 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F99D6E844; Fri, 14 Jul 2017 00:25:00 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 683D4452C; Fri, 14 Jul 2017 00:24:59 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Fri, 14 Jul 2017 00:24:57 +0000 From: Glen Barber To: Mark Johnston Cc: jungle boogie , freebsd-stable@freebsd.org Subject: Re: [SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice Message-ID: <20170714002457.GH16843@FreeBSD.org> References: <1499636909729.64073@secc.org> <20170710192441.3wglwfwv7jpnt7tb@riemann> <20170710194750.xwuopzrwapnh3c6k@riemann> <20170710200005.GA82530@wkstn-mjohnston.west.isilon.com> <20170711054812.GW1935@kib.kiev.ua> <4e0157c3-2eb2-7d7b-a426-9a7da4388334@gmail.com> <20170713130630.GC58943@FreeBSD.org> <20170714000612.GC63588@wkstn-mjohnston.west.isilon.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="qVHblb/y9DPlgkHs" Content-Disposition: inline In-Reply-To: <20170714000612.GC63588@wkstn-mjohnston.west.isilon.com> X-Operating-System: FreeBSD 11.0-STABLE amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer X-Spidey-Sense: Uh oh, Peter logged in User-Agent: Mutt/1.8.2 (2017-04-18) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 00:25:00 -0000 --qVHblb/y9DPlgkHs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 13, 2017 at 05:06:12PM -0700, Mark Johnston wrote: > On Thu, Jul 13, 2017 at 01:06:30PM +0000, Glen Barber wrote: > > On Wed, Jul 12, 2017 at 11:29:05PM -0700, jungle boogie wrote: > > > On 07/10/2017 10:48 PM, Konstantin Belousov wrote: > > > > On Mon, Jul 10, 2017 at 01:00:05PM -0700, Mark Johnston wrote: > > > > > I suspect that this is a result of r320763. That change removed a= field > > > > > from struct vm_map_entry, which is embedded in struct vm_map. Vir= tualbox > > > > > does not reference the fields of struct vm_map directly, but it d= oes > > > > > call vm_map_pmap(), which is an inline accessor. > > > >=20 > > > > Thank you for noting. I do not consider vm_map part of the guarant= eed > > > > stable KBI, but in this case it is simpler to add padding than to f= ollow > > > > principles. > > > >=20 > > > > Fixed in 320889, will ask re for MFS permissions in a day. > > >=20 > > > I think this is the commit: > > > https://svnweb.freebsd.org/base/stable/11/sys/vm/vm_map.h?view=3Dlog&= pathrev=3D320889 > > >=20 > > > Do you think this will get picked up by/for RC3, which will begin on = Friday? > > > https://www.freebsd.org/releases/11.1R/schedule.html > > >=20 > >=20 > > Yes, it will be in RC3. It was committed to releng/11.1 as r320909. >=20 > It should be noted that anyone that recompiled virtualbox for RC2 will > need to do so again after updating to RC3. Anyone going straight from > RC1 or earlier to RC3 ought to be unaffected. >=20 Thank you for mentioning this. I would have forgotten to include this in the RC3 and RELEASE announcement text. I'll make a note of it right now... Glen --qVHblb/y9DPlgkHs Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlloD1QACgkQAxRYpUeP 4pP+nRAAofK9IE4leSFo198urBAcTPQ+SIcaudCxyBKFrMem6q1zjXMwZ2b5R9Hl pEBwC7geywUQLmGj4C7xY0RV42kwVSCpjDB5tpdzzuNckTfuLBe4g1AvQrwn65bA 62rxOO4Cb7uZzoN6Lk4kePXHVOxAm4rlGSrRdhEPpymQ9W5wy1NhKK94necahdrk YMHSfycI6iTt5f6DIT5829EPdPSwn/TX7avbna32P2b8StzGDS9aYC4LzLIGCTza 8j73GQCCSZgP0dFbAJgHRove1NJhidnZ5s0L79YTS+dZZchlBvVGKsA5ZKdVocY2 tRYxPW0udVovq1Tmtz8Jc9ifxb+mqh9aSxn6PoGnwL/d55WNiH6Q2en2VopcyMoZ 5B9lPvjoLUFFy7K5/H7lCXI8P0ZSsXUBzwCYdM8Flq9aHvjGksaOGx8y4dokF0cY RY2QFUMDo4AlCzMAz7PJ/i4AdZxk0cMazMmzk7DvLFek8wDLMFMCGUcdQ35WWzuL ZYfUjY16HvYeEoI1KuOh8c90C0fh3IgpNUP1H0Fbk7rPNkxLhW5KDxeo5rDpImN3 SSAOihllnxI5mu6C0WLuABLZ5WIT6WiXWFp4eWPFgwHqG/KhMM+jOBq8WZRglhLc Bjw6o7NreXMhaNWvXyY25BhIcAKMmGJZeecrx1CVZaJXI+vK2CM= =I92k -----END PGP SIGNATURE----- --qVHblb/y9DPlgkHs--