From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D8448C433E0 for ; Thu, 2 Jul 2020 09:41:46 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id AC8F620760 for ; Thu, 2 Jul 2020 09:41:46 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="Scfqkb+l" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727057AbgGBJlq (ORCPT ); Thu, 2 Jul 2020 05:41:46 -0400 Received: from us-smtp-1.mimecast.com ([205.139.110.61]:44886 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725287AbgGBJlq (ORCPT ); Thu, 2 Jul 2020 05:41:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1593682904; 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: in-reply-to:in-reply-to:references:references; bh=otHkOaIeH581GEjy8u2mxjoQIJ9VnLDjphgnTEOC07k=; b=Scfqkb+lo1dwAIrAnoaR3H6X46G2LEM7YRpC75IQ8cwn97+t0hXGlWB7/Q1EZOuY+16gjM Xb92PzaWv+3/L6Fh3Mo56mnWRYLKR6TVZH8EE+jFBaSdSHaWqoOfhx+iq44UUZj+3CdkDY iaHlUT8fYTUn/8Wntn+icSszS+Qy5Hs= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-170-LtaEbmigPPOIpO_QQDYP5g-1; Thu, 02 Jul 2020 05:41:40 -0400 X-MC-Unique: LtaEbmigPPOIpO_QQDYP5g-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id D7EA1107ACCA; Thu, 2 Jul 2020 09:41:38 +0000 (UTC) Received: from oldenburg2.str.redhat.com (ovpn-112-162.ams2.redhat.com [10.36.112.162]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 5E7C073FDE; Thu, 2 Jul 2020 09:41:37 +0000 (UTC) From: Florian Weimer To: Aleksa Sarai Cc: "Michael Kerrisk \(man-pages\)" , pgajdos , eppers@posteo.de, linux-man , libc-alpha@sourceware.org Subject: Re: openat2.h location (openat2.2) References: <20200630141703.GB12757@laura.suse.cz> <20200630223348.rrr23sfuh7p46top@yavin.dot.cyphar.com> Date: Thu, 02 Jul 2020 11:41:35 +0200 In-Reply-To: <20200630223348.rrr23sfuh7p46top@yavin.dot.cyphar.com> (Aleksa Sarai's message of "Wed, 1 Jul 2020 08:33:48 +1000") Message-ID: <878sg2dzjk.fsf@oldenburg2.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Sender: linux-man-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-man@vger.kernel.org * Aleksa Sarai: > On 2020-06-30, Michael Kerrisk (man-pages) wrote: >> [CC += Aleksa, linux-man@] >> >> Hello Petr, >> >> I'm bringing Aleksa, the creator of the system call, into CC. >> >> Aleksa, the issue is that the header file () documented in >> the manual page that you sent does not (yet) exist (and the bug >> reporter therefore suggests that the manual page should say to include >> . >> >> I'm guessing that there is (or was) a plan to add a header >> file to glibc. What is the status? > > Yes, Florian asked me to put the openat2 definitions into a separate > header (openat2.h) so that it could be just copied by glibc rather than > having to do any more hacks around . We still need to document the original *at functions. 8-( That's a precondition for adding openat2 (which should come with its own documentation right from the start). > I guess those plans haven't come to fruition yet? I'm fine with telling > users to use in the meantime. If we include from the glibc header, the transition should be unproblematic because there won't be any multi-definition errors. Thanks, Florian