From owner-freebsd-stable@FreeBSD.ORG Wed Jul 30 09:55:46 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F8541065679; Wed, 30 Jul 2008 09:55:46 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id 935428FC1A; Wed, 30 Jul 2008 09:55:45 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m6U9tZ5l088540 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Jul 2008 12:55:35 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m6U9tYob015389; Wed, 30 Jul 2008 12:55:34 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2/Submit) id m6U9tYff015388; Wed, 30 Jul 2008 12:55:34 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 30 Jul 2008 12:55:34 +0300 From: Kostik Belousov To: David Southwell Message-ID: <20080730095534.GR97161@deviant.kiev.zoral.com.ua> References: <1217346345.12322.31.camel@bauer.cse.buffalo.edu> <200807300247.34948.david@vizion2000.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lYtTbTuCUQxZgETo" Content-Disposition: inline In-Reply-To: <200807300247.34948.david@vizion2000.net> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Ken Smith , freebsd-stable@freebsd.org, freebsd-current Subject: Re: Upcoming ABI Breakage in RELENG_7 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jul 2008 09:55:46 -0000 --lYtTbTuCUQxZgETo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 30, 2008 at 02:47:34AM -0700, David Southwell wrote: > On Tuesday 29 July 2008 08:45:45 Ken Smith wrote: > > Normally the FreeBSD Project tries very hard to avoid ABI breakage in > > "Stable Branches". However occasionally the fix for a bug can not be > > implemented without ABI breakage, and it is decided that the fix > > warrants the impact of the ABI breakage. We have one of those > > situations coming along for RELENG_7 (what will become FreeBSD 7.1). > > The ABI breakage should only impact kernel modules that are not part of > > the baseline system (those will be patched by the MFC) which deal with > > advisory locks. As such the impact should not cause many people > > problems. > > > > The work that will be MFCed fixes issues with filesystem advisory locks, > > and moves the advisory locks list from filesystem-private data > > structures into the vnode structure. > > > > The MFC will be done by Kostantin Belousov some time this coming Friday > > (August 1st, 2008) if you have concerns and want to watch for it. > > > > Thanks. > Sometimes information gets posted to this list on the assumption that eve= ryone=20 > understand what the writer means. >=20 > This is one of those occasions!! >=20 > For those of us who are not as well informed and experienced as others c= ould=20 > someone please explain what is meant by an ABI breakage, its implication= s=20 > and how to deal with them. The small glitch in the announcement is use of the ABI =3D=3D Application Binary Interface term, that is better be replaced by KBI =3D=3D Kernel Bina= ry Interface. No usermode breakage is expected to result from MFC. The only consequence is the need to adopt some out-of-tree filesystems, not that I am aware of any ATM. If you are the author or maintainer of such module, then you need to watch this out. --lYtTbTuCUQxZgETo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkiQOpUACgkQC3+MBN1Mb4hkrwCgjPiVpsaxrbcY9dNxzkgjlz5y mnMAnAjqc2yGSdsEkfbHm7MnScPocIOp =I0hU -----END PGP SIGNATURE----- --lYtTbTuCUQxZgETo--