Re: [GIT] Networking
From: Marcel Holtmann
Date: Thu Sep 03 2015 - 17:09:48 EST
> Ahh. Google shows that it's an old clang warning that gcc has recently
> picked up.
> But even clang doesn't seem to have any way for a project to say
> "please warn about arrays in function argument declaration". It *is*
> very traditional idiomatic C, it's just that I personally think it's
> one of those bad traditional C things exactly because it's so
> misleading about what actually goes on. But I guess that in practice,
> the only thing that it actually *affects* is "sizeof" (and assignment
> to the variable name - something that would be invalid for a real
> array, but works on argument arrays because they are really just
> The "array as function argument" syntax is occasionally useful
> (particularly for the multi-dimensional array case), so I very much
> understand why it exists, I just think that in the kernel we'd be
> better off with the rule that it's against our coding practices.
I find them useful as syntactic sugar. We have not used them a lot, but there are cases in our crypto handling code where we have fixed size array inputs/outputs and there we opted to use them. They make it easy to remember what the expected sizes of input and output are without having to read through the implementation (of course we never even tried to use sizeof on these pointers).
static int smp_ah(struct crypto_blkcipher *tfm, const u8 irk,
const u8 r, u8 res)
This is one of the simple crypto hashing for privacy keys we have.
r' = padding || r
ah(h, r) = e(k, r') mod 2^24
We are fully aware that const u8 r is const u8 *r. As I said, it is syntactic sugar for us and nothing more.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/