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 1BB5A279DD3 for ; Fri, 5 Sep 2025 09:41:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.133.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1757065304; cv=none; b=fWjDV6Wr2nCJXvQnBku9Yj93o8JS91YDGUvI5w0krajKNCk709CVCn3Yrb381a3Bfo3/pc1XfjnqjMwWKhLEOPaYqBUD5uYwsqw12zXFkKeQyvzlagutPzoady++DP1GKzVi1m8ia3ACCGE0VmhwN9ezDiAuZmY56JCJKRCoCLo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1757065304; c=relaxed/simple; bh=xK0X5ybXdU7CZSUGGi0MOJLoE7ekQvmtxtU/O/I8VeE=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=uDkYhTxLxRz39jJMQjEJO8xdZlI3svgWKHO0gHdFLdOK6z576+HGTEEHUayuabjtloWDaLdKSsof3LiWDYOG0FRDZRFSEDO4mJYblhnERpygwRnZ2veUWkvpSczl7l4Bfyo3FYX56Cx2jCUMFsVf9XdJjyTcQbxMstO2u3OiKFk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=HAnQsOtS; arc=none smtp.client-ip=170.10.133.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="HAnQsOtS" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1757065301; 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=AhBFGiEZQECiCXPQgfE0yM1j7Y3xE+crwyDfNzUa1yA=; b=HAnQsOtSehxjfbFLHgfLjZ5c4lJfHhzk9j2jNttg6A3MwyDPoBQ0kGKsU9URPjf9gq0gr+ 5vNRENy2DaAdx6AfHgstKe4gA4p+m8meP3AZn8uRvd+PJ4wZlXCgT7ioz/LyzovWFVw1dx N4FFleCSYZwDCyl6wuBbfgc4rrvtn+8= Received: from mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (ec2-35-165-154-97.us-west-2.compute.amazonaws.com [35.165.154.97]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-240-BiEXApicPY29oj70ntVMgQ-1; Fri, 05 Sep 2025 05:41:38 -0400 X-MC-Unique: BiEXApicPY29oj70ntVMgQ-1 X-Mimecast-MFC-AGG-ID: BiEXApicPY29oj70ntVMgQ_1757065297 Received: from mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.17]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 7EC83180034F; Fri, 5 Sep 2025 09:41:36 +0000 (UTC) Received: from fweimer-oldenburg.csb.redhat.com (unknown [10.45.224.104]) by mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 9D09419540EB; Fri, 5 Sep 2025 09:41:30 +0000 (UTC) From: Florian Weimer To: Amir Goldstein Cc: Aleksa Sarai , linux-fsdevel@vger.kernel.org, patches@lists.linux.dev, Jeff Layton , Chuck Lever , Alexander Aring , Josef Bacik , Jan Kara , Christian Brauner , Matthew Wilcox , David Howells , linux-api@vger.kernel.org, Kees Cook , Randy Dunlap Subject: Re: [PATCH v3] uapi/linux/fcntl: remove AT_RENAME* macros In-Reply-To: (Amir Goldstein's message of "Fri, 5 Sep 2025 11:17:30 +0200") References: <20250904062215.2362311-1-rdunlap@infradead.org> <2025-09-05-armless-uneaten-venture-denizen-HnoIhR@cyphar.com> Date: Fri, 05 Sep 2025 11:41:27 +0200 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Precedence: bulk X-Mailing-List: linux-fsdevel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 3.0 on 10.30.177.17 * Amir Goldstein: >> If it's too much effort to synchronise them between glibc then it's >> better to just close the book on this whole chapter (even though my >> impression is that glibc made a mistake or two when adding the >> definitions). > > Considering that glibc has this fix lined up: > https://inbox.sourceware.org/libc-alpha/lhubjnpv03o.fsf@oldenburg.str.redhat.com/ > > Do we need to do anything at all? > > Florian, > > I am not that familiar with packaging and distributions of glibc > headers and kernel headers to downstream users. I don't think kernel changes are necessary or desirable at this point. The glibc change went into glibc 2.42 only, and at this point in time, all distributions shipping 2.42 (few of them do) are pretty much guaranteed to pick up fixes from the 2.42 stable release branch regularly. So if we get this into glibc 2.43 and backport it to 2.42, the problem should disappear quite soon from a developer's perspective. Thanks, Florian