[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aKyvO2bvPCZEzuBd@casper.infradead.org>
Date: Mon, 25 Aug 2025 19:45:15 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: linux-kernel@...r.kernel.org, Amir Goldstein <amir73il@...il.com>,
Jeff Layton <jlayton@...nel.org>,
Chuck Lever <chuck.lever@...cle.com>,
Alexander Aring <alex.aring@...il.com>,
Josef Bacik <josef@...icpanda.com>,
Aleksa Sarai <cyphar@...har.com>, Jan Kara <jack@...e.cz>,
Christian Brauner <brauner@...nel.org>,
linux-fsdevel@...r.kernel.org, linux-api@...r.kernel.org
Subject: Re: [PATCH] uapi/fcntl: conditionally define AT_RENAME* macros
On Mon, Aug 25, 2025 at 10:52:31AM -0700, Randy Dunlap wrote:
> $ grep -r AT_RENAME_NOREPLACE /usr/include
> /usr/include/stdio.h:# define AT_RENAME_NOREPLACE RENAME_NOREPLACE
> /usr/include/linux/fcntl.h:#define AT_RENAME_NOREPLACE 0x0001
>
> I have libc 2.42-1.1 (openSUSE).
I wonder if we can fix it by changing include/uapi/linux/fcntl.h
from being an explicit 0x0001 to RENAME_NOREPLACE? There's probably
a horrendous include problem between linux/fcntl.h and linux/fs.h
though?
Powered by blists - more mailing lists