From owner-freebsd-hackers@freebsd.org Mon Jul 13 09:13:43 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 74DD33B59 for ; Mon, 13 Jul 2015 09:13:43 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 339F91ABD; Mon, 13 Jul 2015 09:13:43 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by qkdv3 with SMTP id v3so54573850qkd.3; Mon, 13 Jul 2015 02:13:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7IEA//zyfbMMipD9/BtZaDoyiZ8uJYRcURf4936jFQ4=; b=IoSDeGTWRkt/uoMuOtbQHAtn2T9UKpG5DPVQ45b8qu4uY+jRFRyBLv1YPV9szQ4Gb4 bC1McEVce/HlIROBB+iSh8HFQ7cunt8UUaS1RUwMzZaImWyFp/dRMyMHbg01LStuCc5Q B6lrpGlMhz0uXFGWXJ5tNdr1cGUzupvCA5rQvAee5G4Jfk6JEOcpqdTQWzAVUKrix7yl iTD7lBQl43MwH9TJ0jxoqi7WQP4AAZzJFakbA1Mne350+BrUr/Q8eArr2LsmvK9Aw0bV zH7mduzoiDMZUzvjXyx0e2hI9AdaTtVXEn5uUUuBpMoJWwYvANWNbjevYbO/+qOk7hKQ Ej7Q== MIME-Version: 1.0 X-Received: by 10.140.151.203 with SMTP id 194mr30567742qhx.80.1436778822257; Mon, 13 Jul 2015 02:13:42 -0700 (PDT) Received: by 10.140.98.73 with HTTP; Mon, 13 Jul 2015 02:13:42 -0700 (PDT) In-Reply-To: <55A33A8A.6070505@freebsd.org> 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> Date: Mon, 13 Jul 2015 02:13:42 -0700 Message-ID: Subject: Re: Fix MNAMELEN or reimplement struct statfs From: NGie Cooper To: Julian Elischer Cc: freebsd , Kirk McKusick Content-Type: text/plain; charset=UTF-8 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 09:13:43 -0000 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!