From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk0-f175.google.com ([209.85.220.175]:34434 "EHLO mail-qk0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752406AbcHQSXM (ORCPT ); Wed, 17 Aug 2016 14:23:12 -0400 Received: by mail-qk0-f175.google.com with SMTP id t7so26123726qkh.1 for ; Wed, 17 Aug 2016 11:23:11 -0700 (PDT) Message-ID: <1471458189.3196.68.camel@redhat.com> Subject: Re: [glibc PATCH] fcntl: put F_OFD_* constants under #ifdef __USE_FILE_OFFSET64 From: Jeff Layton To: Joseph Myers Cc: libc-alpha@sourceware.org, linux-fsdevel@vger.kernel.org, Michael Kerrisk , Carlos O'Donell , Yuriy Kolerov Date: Wed, 17 Aug 2016 14:23:09 -0400 In-Reply-To: References: <1471445251-2450-1-git-send-email-jlayton@redhat.com> <1471456198.3196.43.camel@redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, 2016-08-17 at 17:56 +0000, Joseph Myers wrote: > On Wed, 17 Aug 2016, Jeff Layton wrote: > > > > > The only difference between struct flock and flock64 is the size of the > > offset values. So, I think that __OFF_T_MATCHES_OFF64_T would suffice > > Well, MIPS has e.g.: > > #if _MIPS_SIM != _ABI64 >     /* The 64-bit flock structure, used by the n64 ABI, and for 64-bit >        fcntls in o32 and n32, never has this field.  */ >     long int l_sysid; > #endif > > Now, this doesn't actually cause issues, because __OFF_T_MATCHES_OFF64_T  > isn't true for o32 or n32, and the layouts are indeed the same for n64.   > But you need to check every architecture to make sure there aren't any  > such issues that mean __OFF_T_MATCHES_OFF64_T is the wrong condition. > Yeah, I saw that but all of that is down inside the pad that the kernel doesn't really care about. The important bits are the parts up to and including the pid field. I did go through all of them before mentioning that and I still think it is sufficient, but I certainly wouldn't mind having someone sanity check me here! -- Jeff Layton