From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E095F29CA for ; Mon, 6 Mar 2023 10:19:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1678097985; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=N5kPdPwD+Yzzq1F/6gHSCohrp0LQDJVtVAgwUDdIgzo=; b=btAjb/tFdD+j13mVEaPyEahxYIAlz+Y3VdQj5kt02FWU3zoYRgSa3H+GnDVqQ5cLH6Nflm YARLGYVq17On6v9hT10k4BKqsG8ndDF2DnjD+cpQ18n2EHICnh2NyHvBZV/jlIo7Voil/n npS1ipo9lSulOu9Gde5CiJ1l11vKli4= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-240-G7Chke4tN2KmYJ0N0gncAg-1; Mon, 06 Mar 2023 05:19:40 -0500 X-MC-Unique: G7Chke4tN2KmYJ0N0gncAg-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 124F385A588; Mon, 6 Mar 2023 10:19:40 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.2.16.80]) by smtp.corp.redhat.com (Postfix) with ESMTPS id F1F541121314; Mon, 6 Mar 2023 10:19:37 +0000 (UTC) From: Florian Weimer To: Andreas Schwab via Libc-alpha Cc: Paul Eggert , Andreas Schwab , Daniel P. =?utf-8?Q?Berrang=C3=A9?= , Demi Marie Obenour , Eric Blake , Sam James , autoconf@gnu.org, c-std-porting@lists.linux.dev, Zack Weinberg , David Seifert , Gentoo Toolchain , Arsen =?utf-8?Q?Arsenovi=C4=87?= , rjones@redhat.com Subject: Re: On time64 and Large File Support References: <20230301223859.chl5o3bedqckf3tx@redhat.com> <086d6fcd-3738-cc7f-db72-6a8d19d33e30@gmail.com> <7253e4c5-0f36-e725-f180-624f8887bf08@cs.ucla.edu> Date: Mon, 06 Mar 2023 11:19:36 +0100 In-Reply-To: (Andreas Schwab via Libc-alpha's message of "Mon, 06 Mar 2023 09:58:01 +0100") Message-ID: <87r0u2w5af.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) Precedence: bulk X-Mailing-List: c-std-porting@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.3 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable * Andreas Schwab via Libc-alpha: > On M=C3=A4r 02 2023, Paul Eggert wrote: > >> Another thing that's different is that when off_t grew in the 1990s, >> people said they needed a wider off_t RIGHT NOW, because programs wouldn= 't >> work on large inputs otherwise. > > That is only true for rather few selected programs. It depends on the system configuration. For some file systems, inode numbers outside the 32-bit range can be quite common. This impacts 32-bit applications even if they never use ino_t because functions such as fstat and readdir cannot know that these fields are unused. We've been working around this for our 32-bit builders with special file system configuration because like many, we do not build everything with -D_FILE_OFFSET_BITS=3D64. Thanks, Florian