Date: Thu, 2 Jan 2014 21:26:12 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: John-Mark Gurney <jmg@funkthat.com> Cc: src-committers@FreeBSD.org, Pawel Jakub Dawidek <pjd@FreeBSD.org>, svn-src-all@FreeBSD.org, Alfred Perlstein <bright@mu.org>, Stanislav Sedov <stas@FreeBSD.org>, svn-src-head@FreeBSD.org Subject: Re: svn commit: r255219 - in head: contrib/tcpdump lib/libc lib/libc/capability lib/libc/include lib/libc/sys lib/libprocstat sbin/dhclient sbin/hastd sys/amd64/linux32 sys/bsm sys/cddl/compat/opensola... Message-ID: <20140102192612.GM59496@kib.kiev.ua> In-Reply-To: <20140102191420.GB99167@funkthat.com> References: <201309050009.r8509vsE061271@svn.freebsd.org> <67DFFD7B-01DE-4862-BED3-DD42EB92A8F4@freebsd.org> <20140102093322.GA1655@garage.freebsd.pl> <52C53F69.3040507@mu.org> <20140102104904.GB1655@garage.freebsd.pl> <20140102131308.GI59496@kib.kiev.ua> <20140102191420.GB99167@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--r+soi4lT5gbz/qtX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 02, 2014 at 11:14:20AM -0800, John-Mark Gurney wrote: > Konstantin Belousov wrote this message on Thu, Jan 02, 2014 at 15:13 +020= 0: > > > > Afaik you could just remove the "spare" and steal 2 or 4 entries fr= om=20 > > > > _kf_ispare until it is sorted. > > >=20 > > > Yes, this would work for current cap_rights_t structure, at least for > > > i386 and amd64, but would only allow to expand the structure by one > > > uint64_t in the future (which might or might not be enough). The > > > cap_rights_t structure is designed to be expanded to 5 uint64_ts with= out > > > breaking ABI. I don't want to stuck with current cap_rights_t that is > > > designed to expand, but cannot be, because kinfo_file wasn't modified= at > > > the start of a major branch. > > The ABI stability is not limited to the single branch. It must be > > preserved across whole project lifetime. >=20 > Umm. when did this policy change happen? I thought ABI compatibility > was limited to major releases of FreeBSD? How are you suppose to do > any work if you can't break ABI ever? Policy did not changed. Breaking ABI was never allowed, except for the kernel management interfaces. Later was only accepted due to tight relation of the typical management facilities and internal kernel structures, but this is considered a bug. >=20 > I did a quick search for "freebsd policy abi breakage" and found some > mailing list posts about this, but no authoritative statement... Re tried to write down the policy, last time it was several years ago. The efforts should be revived. >=20 > Of course the problem is that when we move to > (ASN.1/libnv/ctf/YAML/JSON/XML/etc) we will break ABI compatibility too, > or introduce tons of compatibility code that will rot... I do not understand what are you trying to say. --r+soi4lT5gbz/qtX Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBAgAGBQJSxb1TAAoJEJDCuSvBvK1B/zQP/iVk7VZOtU9854qp4PlvNB1M 9WjhnhwCjhpfvmZr82Izq3fTbr58vytLcQvZYbY8iwbEr3EJcyF5Z1qNnDqd4cMW Wr0K4nTtfprHl6UFvDqHobTRq4/1/QMSZliavHbOhmIAvFXRsL6NwsiFOoTKtGe7 uTWTRoOB/U0IuCXJ39x18nTVAJ6ChJKOZCirTJ0FGJRg0Okalux2Ynci59Ec/69P hm8m71Lfi9NeLx+7HbQctK9RAA7p0S9D7Z0qHBoncGR17cevf6YrQYZaFvQMLIsx s5UCoVfde0UOqVORDu7qP4fuehp2i82y0+mxmBukTyQZO72Lj84ptosHR+m8jrwk TbO34VMhOTCwnxdBZoY0HO5v8bcTFoH+f/MlaX8QTFP2EdJRgN0+cfmsl2SSvzLB kcEPZXeqDss2SNkwejqhxcUEdz+qrHIeqs9uUeyAzgKkyTpTe+vOkJXp6lWIEUhU 2Vbf7ooBbzWZX78TcOfktej2dKN+pq2FerdO0XrPunA0hS5uoswKZuSssDKC4DY+ DZGdzbeWDvDQUdxAY4s1JtdIWiAGK7u6ma567h2gdb69SiP06I2vEEbZKhP6YEpi sRhC4ynLX9/xrmnDZ7rhFysfr7HtAxcKgL+mIgfnP+XFu1yy7DtMSiHTVjNm7TFA gmvKDsqCnHTvShzW+jOy =CWBK -----END PGP SIGNATURE----- --r+soi4lT5gbz/qtX--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140102192612.GM59496>