From owner-freebsd-stable@freebsd.org Fri Jul 31 15:45:11 2015 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 85CB19AF66C for ; Fri, 31 Jul 2015 15:45:11 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 752041DC1; Fri, 31 Jul 2015 15:45:11 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 032EF1971; Fri, 31 Jul 2015 15:45:10 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Fri, 31 Jul 2015 15:45:09 +0000 From: Glen Barber To: freebsd-stable@FreeBSD.org Cc: FreeBSD Release Engineering Team Subject: Re: HEADS-UP: PCI ID driver conflict with ahd(4) and pms(4) Message-ID: <20150731154509.GB90754@FreeBSD.org> References: <20150731014832.GN90754@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="IQ2ZtBPOZQVGoXc0" Content-Disposition: inline In-Reply-To: <20150731014832.GN90754@FreeBSD.org> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 31 Jul 2015 15:45:11 -0000 --IQ2ZtBPOZQVGoXc0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 31, 2015 at 01:48:32AM +0000, Glen Barber wrote: > The new driver for PMC Sierra SAS/SATA HBAs does not properly validate > that both the vendor ID and device ID of some storage device drivers. > At present, we know there is a conflict with ahd(4), it is possible > there are more. >=20 The pms(4) driver was pulled from GENERIC in head (r286131) and stable/10 (r286132). I am awaiting a response within re@ to make this change in releng/10.2, after which the 10.2-RC2 builds will be restarted to include this change, as this is entirely too dangerous to allow by default. As such, there will be delay with the 10.2-RC2 availability. Glen On behalf of: re@ --IQ2ZtBPOZQVGoXc0 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVu5gFAAoJEAMUWKVHj+KTJ+cP/28jDFjq4c/O0dYdC4wh8yrr MPJ2J4OcUEXh7ZTl0deN4+wdQbxRxixiVQndE7ztaoKIx0uJk31Eihw5FFZWECMy Lx/fnfPu97thbqzmWRsITTQpfPenmSh3Xbt3n0z2dc55Z3FuBrK3mAKphUbIxEXS lQq5B8xPAAYK5p5DXCMjzMxNwmHjdlclVDjzlVCkIFKtDxFDqvZzWlrOlptrI3D2 Qx0uD5+IHVWWhcw/aVKeDCsAfww5NWJ2cIsgl4lzlOllNJMs9FnzHLFaTwm2sV2h Q82Cz6F224qZzncKLIfiinkfCQKYTno5YbRZPV8Ydi7NpNG2OH6Vku4E7YSaTRP0 Su9Ci8qzsuiYXPGjq72o32w96fXsgitDX9VoXAdKhUYzH6ftNh38esCQgmGLIc97 0BR9uYFbZlbvdDZGL766Ae4O96fnIbwkDRZhRyh4s/rXH9iiZn6/d4s75vfjszy4 DsY0+qA3GjVo+BYyAku3rY07m8/dRmJoDa3B84hmuEsJiAuk8MQUpAcecgpZSVHE t1XJzZjCPE/xIsg0z9HRAC+8bllteWJHVKb3E8o29VKgtSsCgt4qz2+FTZaQumx/ E1Rpa0Ws9K7+qguuVr0yYmdYZ5PjKNaWIv0cbXPScy7C760oVFKr8VDyDLR12uqW USV7PLvktseRHvJ//QLI =WbF8 -----END PGP SIGNATURE----- --IQ2ZtBPOZQVGoXc0--