linux-kernel - Re: Q: crypto/cipher.c

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]

Date:	Mon, 20 Apr 2009 19:41:35 +0100
From:	Paulo Marques <pmarques@...popie.com>
To:	H Hartley Sweeten <hartleys@...ionengravers.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Q: crypto/cipher.c

H Hartley Sweeten wrote:
> Hello all,

Hi,

> I have a question about the following code in crypto/cipher.c.
> 
> static void cipher_crypt_unaligned(void (*fn)(struct crypto_tfm *, u8 *,
> 					      const u8 *),
> 				   struct crypto_tfm *tfm,
> 				   u8 *dst, const u8 *src)
> {
> 	unsigned long alignmask = crypto_tfm_alg_alignmask(tfm);
> 	unsigned int size = crypto_tfm_alg_blocksize(tfm);
> 	u8 buffer[size + alignmask];
> 	u8 *tmp = (u8 *)ALIGN((unsigned long)buffer, alignmask + 1);
> 
> 	memcpy(tmp, src, size);
> 	fn(tfm, tmp, tmp);
> 	memcpy(dst, tmp, size);
> }
> 
> Doesn't the size of buffer need to be known at compile time for this
> to actually work? Or do alignmask and size work out to be constants?
> 
> This appears to be buggy. But I may just be missing something...

It's a GCC extension:

http://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html

-- 
Paulo Marques - www.grupopie.com

"All generalizations are false."
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/