From: Jeff Layton <jlayton@kernel.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Chuck Lever" <chuck.lever@oracle.com>,
"Alexander Aring" <alex.aring@gmail.com>,
"Jan Kara" <jack@suse.cz>,
"Christian Brauner" <brauner@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vfs: use UAPI types for new struct delegation definition
Date: Wed, 03 Dec 2025 09:01:55 -0500 [thread overview]
Message-ID: <f595e7e845bc7f52c0a2c8978e3e81e860faeb71.camel@kernel.org> (raw)
In-Reply-To: <20251203-uapi-fcntl-v1-1-490c67bf3425@linutronix.de>
On Wed, 2025-12-03 at 14:57 +0100, Thomas Weißschuh wrote:
> Using libc types and headers from the UAPI headers is problematic as it
> introduces a dependency on a full C toolchain.
>
> Use the fixed-width integer types provided by the UAPI headers instead.
>
> Fixes: 1602bad16d7d ("vfs: expose delegation support to userland")
> Fixes: 4be9e04ebf75 ("vfs: add needed headers for new struct delegation definition")
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> ---
> include/uapi/linux/fcntl.h | 10 +++-------
> 1 file changed, 3 insertions(+), 7 deletions(-)
>
> diff --git a/include/uapi/linux/fcntl.h b/include/uapi/linux/fcntl.h
> index 5e277fd955aa..aadfbf6e0cb3 100644
> --- a/include/uapi/linux/fcntl.h
> +++ b/include/uapi/linux/fcntl.h
> @@ -4,11 +4,7 @@
>
> #include <asm/fcntl.h>
> #include <linux/openat2.h>
> -#ifdef __KERNEL__
> #include <linux/types.h>
> -#else
> -#include <stdint.h>
> -#endif
>
> #define F_SETLEASE (F_LINUX_SPECIFIC_BASE + 0)
> #define F_GETLEASE (F_LINUX_SPECIFIC_BASE + 1)
> @@ -90,9 +86,9 @@
>
> /* Argument structure for F_GETDELEG and F_SETDELEG */
> struct delegation {
> - uint32_t d_flags; /* Must be 0 */
> - uint16_t d_type; /* F_RDLCK, F_WRLCK, F_UNLCK */
> - uint16_t __pad; /* Must be 0 */
> + __u32 d_flags; /* Must be 0 */
> + __u16 d_type; /* F_RDLCK, F_WRLCK, F_UNLCK */
> + __u16 __pad; /* Must be 0 */
> };
>
> /*
>
> ---
> base-commit: 3f9f0252130e7dd60d41be0802bf58f6471c691d
> change-id: 20251203-uapi-fcntl-f49d5b30f8cd
>
> Best regards,
Thanks. I wasn't sure of the right way to do this.
Acked-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2025-12-03 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 13:57 Thomas Weißschuh
2025-12-03 14:01 ` Jeff Layton [this message]
2025-12-03 14:14 ` Arnd Bergmann
2025-12-04 6:58 ` Thomas Weißschuh
2025-12-04 9:09 ` Arnd Bergmann
2025-12-04 9:02 ` Christian Brauner
2025-12-04 9:17 ` Thomas Weißschuh
2025-12-05 8:52 ` Christian Brauner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f595e7e845bc7f52c0a2c8978e3e81e860faeb71.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=alex.aring@gmail.com \
--cc=arnd@arndb.de \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.weissschuh@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®