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] [day] [month] [year] [list]
Message-ID: <176125134618.2701009.7020323237839096671.b4-ty@kernel.org>
Date: Thu, 23 Oct 2025 22:31:18 +0200
From: Nicolas Schier <nsc@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
	Rasmus Villemoes <linux@...musvillemoes.dk>,
	Nathan Chancellor <nathan@...nel.org>
Cc: Nicolas Schier <nsc@...nel.org>,
	Nick Desaulniers <nick.desaulniers+lkml@...il.com>,
	Bill Wendling <morbo@...gle.com>,
	Justin Stitt <justinstitt@...gle.com>,
	jfs-discussion@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org,
	llvm@...ts.linux.dev,
	Dave Kleikamp <dave.kleikamp@...cle.com>
Subject: Re: [PATCH] jfs: Rename _inline to avoid conflict with clang's '-fms-extensions'


On Thu, 23 Oct 2025 10:38:50 -0700, Nathan Chancellor wrote:
> After commit 778740ee2d00 ("Kbuild: enable -fms-extensions"), building
> fs/jfs fails with clang:
> 
>   In file included from fs/jfs/jfs_unicode.c:8:
>   fs/jfs/jfs_incore.h:86:13: error: type name does not allow function specifier to be specified
>      86 |                                         unchar _inline[128];
>         |                                                ^
>   fs/jfs/jfs_incore.h:86:20: error: expected member name or ';' after declaration specifiers
>      86 |                                         unchar _inline[128];
>         |                                         ~~~~~~~~~~~~~~^
> 
> [...]

Applie to kbuild-next, thanks!

[1/1] jfs: Rename _inline to avoid conflict with clang's '-fms-extensions'
      commit: 9b38933a351d4f4e95a192adfe21ec235632bf4c

Please note that commit hashes might change in case of issues with
kbuild-next branch.

Best regards,
-- 
Nicolas


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ