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-next>] [day] [month] [year] [list]
Message-ID: <20251020140735.39084e85@canb.auug.org.au>
Date: Mon, 20 Oct 2025 14:07:35 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: Meenakshi Aggarwal <meenakshi.aggarwal@....com>, Pankaj Gupta
 <pankaj.gupta@....com>, Linux Crypto List <linux-crypto@...r.kernel.org>,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
 Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: build warning after merge of the crypto tree

Hi all,

After merging the crypto tree, today's linux-next build (x86_64
allmodconfig) produced this warning:

security/keys/trusted-keys/trusted_caam.c: In function 'dump_options':
security/keys/trusted-keys/trusted_caam.c:37:20: note: the ABI of passing struct with a flexible array member has changed in GCC 4.4
   37 | static inline void dump_options(struct caam_pkey_info pkey_info)
      |                    ^~~~~~~~~~~~

Introduced by commit

  9eb25ca6c973 ("KEYS: trusted: caam based protected key")

I am not sure what to do about this.  It would be nice if we could
suppress the note as we do not support gcc 4.4 any more.  Otherwise,
I suspect that converting the pkey_info argument to a pointer will get
rid of the note.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ