From owner-freebsd-arch@FreeBSD.ORG Fri Mar 22 22:28:57 2013 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B738E5AE for ; Fri, 22 Mar 2013 22:28:57 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 3141D14B for ; Fri, 22 Mar 2013 22:28:56 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.6/8.14.6) with ESMTP id r2MMSnDH036044; Sat, 23 Mar 2013 00:28:49 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.0 kib.kiev.ua r2MMSnDH036044 Received: (from kostik@localhost) by tom.home (8.14.6/8.14.6/Submit) id r2MMSlFT036043; Sat, 23 Mar 2013 00:28:47 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 23 Mar 2013 00:28:47 +0200 From: Konstantin Belousov To: Gleb Kurtsou Subject: Re: Increase the mount path to MAXPATHLEN? Message-ID: <20130322222847.GY3794@kib.kiev.ua> References: <20130319201145.GA19260@ambrisko.com> <20130320102116.GA3794@kib.kiev.ua> <20130321034340.GA1120@reks> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KTQgUyhRQoRwtLfu" Content-Disposition: inline In-Reply-To: <20130321034340.GA1120@reks> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: arch@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Mar 2013 22:28:57 -0000 --KTQgUyhRQoRwtLfu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 20, 2013 at 08:43:40PM -0700, Gleb Kurtsou wrote: > On (20/03/2013 12:21), Konstantin Belousov wrote: > > On Tue, Mar 19, 2013 at 01:11:45PM -0700, Doug Ambrisko wrote: > > > I have a patch at: > > > http://people.freebsd.org/~ambrisko/statf.patch > > > that people can glance at. If this approach is the right way to go > > > then I update it for the latest -current and update it. > >=20 > > No, I do not think this is the right approach. > > You are breaking the ABI in the backward-incompatible way. > >=20 > > What should be done is versioning the fstatfs(2) and other related > > symbols from libc. Please look at the lib/libc/include/compat.h > > and its use for upgrading the syscalls ABI. >=20 > MNAMELEN switch to 1024 was implemented during GSoc 2011. > https://github.com/glk/freebsd-ino64/commit/f2b990cf8861bb72d4477b39426cb= e33f95ffcdf >=20 > freebsd-ino64 repo should contain most recent code, I'll double check > during weekend. It also contains patch to change dev_t to 64 bit. >=20 > https://github.com/glk/freebsd-ino64/commits/projects/ino64 >=20 > Konstantin, do you think it's worth pushing ino64 into CURRENT > considering 10.0 is approaching? The only unresolved issue I can recall > is ABI breakage in audit syscalls, providing compat shims for them > wasn't straightforward due to complex structure. Yes, I do think that ino_t should be finally fixed. Also, please do commit the ABI checking tool to svn. >=20 > Unfortunately I've been swamped at $JOB for a while now and had no time > to clean it up and commit. So if somebody is willing to help please > contact me. What do you need ? What is the estimated time for making this done ? >=20 > > Also, the whole ABI of the system should be inspected for the changes, > > due to possible use of the struct statfs in other structures, or as > > an argument to other functions. > >=20 > > Gleb Kurtsou (gleb@) has a tool which could compare a set of the shlibs > > before and after change for the ABI drift, using the dward debugging > > information. I do not remember where it is stored, definitely worth > > committing somewhere at tools/tools. >=20 > https://github.com/glk/shlib-compat >=20 --KTQgUyhRQoRwtLfu Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBAgAGBQJRTNsfAAoJEJDCuSvBvK1BHkYQAKXvOOjR4O1U5Sz79ot2Ntfs /x7e6HzepTn2XKnGieOw1jtX74jw6PtoswvP0eXCAPRtBZVOCngDoLeOiK4dr4QV SBFIuUxyvNmx8ChrL/AhI3XUqvNOv01VQ5r6axZoDQMPWQbbSPO5NidV7DScsa4m nHs+ZBndUEuUIeImCR25hIKNIecbD5kWLJawMOArdRF2j/Iq8LbwLPu/nVAqURoE +8A1jcZaLJ4lJLLgOu1h2wlUJPhY/Dds0Q2xBvip+20MezIBjmRXtrS4DSvOXSu0 14RhXQ3zxRC8IBW//+gjchviITbC4YRzh3ICO/rbiZqbzalqHBc5yRbNztJ+IlRh VYFe7BbOGwlweEp1JGTnrjPkOblagGPwR3NySlCduDJMzsjwHiswJ9wn1XH4Vi+6 ZiBANKz2b/XxQs/7ezchaQ46dorInif9IcV8iKNK0HYxG8nFE5KRFUXVkT1EcBls kGepg6Ygz+0imtN2UxPUpuDqqzvu3a41yaDVE7spKsBTbg5kV2oHAfF76B/wieYw bCfjuAPG44GeswceCVeBYXTPtsMgyDqxUabXH39gzGtSOIFUWwoAwppR2QPnFHzq qjGRvTnZJ9flfRN/utzSQaryQa95FXAz0KcAlF745PkdLobL47KGtE0RXCUkW6Ax zc6DU8/spK+S1lwq+sUx =bm8H -----END PGP SIGNATURE----- --KTQgUyhRQoRwtLfu--