linux-kernel - Re: [PATCH v2] fuse: uapi: use UAPI types

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJfpegtMXJd_k2j6kgNXNnRRJMPcX=o+yx9C3d_wkK8dtNQT2Q@mail.gmail.com>
Date: Mon, 5 Jan 2026 13:45:21 +0100
From: Miklos Szeredi <miklos@...redi.hu>
To: Thomas Weißschuh <thomas.weissschuh@...utronix.de>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH v2] fuse: uapi: use UAPI types

On Tue, 30 Dec 2025 at 13:11, Thomas Weißschuh
<thomas.weissschuh@...utronix.de> wrote:
>
> Using libc types and headers from the UAPI headers is problematic as it
> introduces a dependency on a full C toolchain.

Can you please elaborate?

Is there a real use case that is being fixed by this?

Or is this some theoretical thing?

Thanks,
Miklos