From owner-freebsd-hackers@freebsd.org Mon Jul 13 15:53:56 2015 Return-Path: Delivered-To: freebsd-hackers@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 4536599BDDF for ; Mon, 13 Jul 2015 15:53:56 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id F0D161DA8; Mon, 13 Jul 2015 15:53:54 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA24949; Mon, 13 Jul 2015 18:51:31 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1ZEg0x-000Fh7-CD; Mon, 13 Jul 2015 18:51:31 +0300 Message-ID: <55A3DE4A.4050102@FreeBSD.org> Date: Mon, 13 Jul 2015 18:50:34 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: NGie Cooper , Kirk McKusick CC: Julian Elischer , freebsd Subject: Re: Fix MNAMELEN or reimplement struct statfs References: <20140415233133.GA14686@ambrisko.com> <5452600C.5030003@omnilan.de> <20141101154004.GA40398@ambrisko.com> <559FD426.3000108@omnilan.de> <20150710154654.GA71708@ambrisko.com> <55A33A8A.6070505@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jul 2015 15:53:56 -0000 On 13/07/2015 12:13, NGie Cooper wrote: > On Sun, Jul 12, 2015 at 9:11 PM, Julian Elischer wrote: >> this hits us occasionally too >> Kirk, you are mentioned here as having a finger in this pie. >> >> do we have a suggested way forward? > > Alternatively, is the ino64_t work slated for CURRENT anytime soon (if > it was before 11.0-RELEASE that would be best probably...). > Thanks! I also would love to see MNAMELEN work in head as soon as possible. I am personally not that much interested in ino64_t, but it would be great as well. -- Andriy Gapon