From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from albireo.enyo.de ([5.158.152.32]:49675 "EHLO albireo.enyo.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756599AbcHYMtg (ORCPT ); Thu, 25 Aug 2016 08:49:36 -0400 From: Florian Weimer To: Christoph Hellwig Cc: Jeff Layton , linux-fsdevel@vger.kernel.org, libc-alpha@sourceware.org, chrubis@suse.cz Subject: Re: [Linux PATCH] fcntl: add new F_OFD_*32 constants and handle them appropriately References: <1471521804-4291-1-git-send-email-jlayton@redhat.com> <20160818170508.GA897@lst.de> <1471541300.2504.23.camel@redhat.com> <20160818173139.GA1140@lst.de> Date: Thu, 25 Aug 2016 13:53:08 +0200 In-Reply-To: <20160818173139.GA1140@lst.de> (Christoph Hellwig's message of "Thu, 18 Aug 2016 19:31:39 +0200") Message-ID: <87bn0ht68r.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-fsdevel-owner@vger.kernel.org List-ID: * Christoph Hellwig: > On Thu, Aug 18, 2016 at 01:28:20PM -0400, Jeff Layton wrote: >> That was my original thinking, but several people seemed to think that >> we should just go ahead and support it. TBH, I don't much care either >> way, but we either need to support it properly, or ensure that trying >> to use OFD locks in a non-LFS program fails to compile. > > Yes, that's what glibc folks should do for now given that they still > seem to refuse being draggred into the present. Your assumptions are wrong, at least for some (many?) of us. 32-bit architectures are legacy; giving them a 64-bit off_t (or even time_t) does not really change that. A hard ABI transition is simply not worth the effort.