Re: [PATCH 21/21] MODSIGN: Apply signature checking to modules on module load [ver #3]

2011-12-12 Thread Rusty Russell
On Mon, 12 Dec 2011 01:21:40 +, David Howells dhowe...@redhat.com wrote: Rusty Russell ru...@ozlabs.org wrote: I think you misunderstand, I'm talking about the modinfo command, not the .modinfo section. Sorry, yes. But why do you need to enhance modinfo? I was suggesting that you

Re: [PATCH 21/21] MODSIGN: Apply signature checking to modules on module load [ver #3]

2011-12-12 Thread David Howells
Rusty Russell ru...@ozlabs.org wrote: OK, then you need to generate stripped modules as part of the build, too. It's a bit of a pain, sure, but hardly a showstopper. They'd have to be maximally stripped so that mkinitrd doesn't do anything to them, but you'd then get the debuginfo from them

Re: [PATCH 1/1] Added CRYPTO_ALG_KERN_DRIVER_ONLY flag.

2011-12-12 Thread Kim Phillips
On Sun, 11 Dec 2011 13:26:26 +0100 Nikos Mavrogiannopoulos n...@gnutls.org wrote: The added CRYPTO_ALG_KERN_DRIVER_ONLY flag indicates whether a cipher is only available via a kernel driver. If the cipher implementation might be available by using an instruction set or by porting the kernel

[PATCH 1/7] crypto: talitos - fix bad kfree

2011-12-12 Thread Kim Phillips
Fix a kfree to an invalid address which causes an oops when running on SEC v2.0 h/w (introduced in commit 702331b crypto: talitos - add hmac algorithms). Signed-off-by: Kim Phillips kim.phill...@freescale.com --- drivers/crypto/talitos.c |8 1 files changed, 4 insertions(+), 4

[PATCH 7/7] crypto: caam - remove DECO access initialization code

2011-12-12 Thread Kim Phillips
Access to the SEC4 DECOs (DEscriptor COntrollers) (for debug purposes) isn't supported or used, and its register access initialization code erroneously makes illegal i/o accesses that show up as errors when run under simulation. Remove it until proper support (via DECORR) is added.

[PATCH 6/7] crypto: caam - fix polarity of propagate error logic

2011-12-12 Thread Kim Phillips
the polarity of the definition for error propagation was reverse in the initial desc.h. Fix desc.h and its users. Signed-off-by: Kim Phillips kim.phill...@freescale.com --- drivers/crypto/caam/caamalg.c | 10 +- drivers/crypto/caam/desc.h|4 ++--

[PATCH 5/7] crypto: caam - more desc.h cleanups

2011-12-12 Thread Kim Phillips
manual removal of double-spaces - no non-whitespace changes. Signed-off-by: Kim Phillips kim.phill...@freescale.com --- drivers/crypto/caam/desc.h | 335 ++-- 1 files changed, 167 insertions(+), 168 deletions(-) diff --git a/drivers/crypto/caam/desc.h

Re: [PATCH 14/14] crc32: Select an algorithm via kconfig

2011-12-12 Thread Darrick J. Wong
On Fri, Dec 02, 2011 at 06:36:46PM -0800, Darrick J. Wong wrote: On Fri, Dec 02, 2011 at 08:25:05AM +0800, Herbert Xu wrote: On Thu, Dec 01, 2011 at 12:15:17PM -0800, Darrick J. Wong wrote: Allow the kernel builder to choose a crc32* algorithm for the kernel. Signed-off-by: Darrick J.

drivers/crypto/picoxcell_crypto.c: boolean and / or confusion

2011-12-12 Thread Joe Perches
On Tue, 2011-12-13 at 00:06 +0100, roel wrote: The test not [val1] or not [val2] always evaluates to true Hey Jamie and Roel Looking at drivers with: $ grep -rP --include=*.[ch] (\b[\w\[\]\\._\-]+)\s*\!\=\s*[\w\[\]\\._\-]+\s*\|\|\s*\1\s*\!\= drivers drivers/crypto/picoxcell_crypto.c: if

drivers/media/video/s5p-fimc/fimc-capture.c: boolean and / or confusion

2011-12-12 Thread Joe Perches
On Tue, 2011-12-13 at 00:06 +0100, roel wrote: The test not [val1] or not [val2] always evaluates to true Hello Looking at drivers with: $ grep -rP --include=*.[ch] (\b[\w\[\]\\._\-]+)\s*\!\=\s*[\w\[\]\\._\-]+\s*\|\|\s*\1\s*\!\= drivers drivers/media/video/s5p-fimc/fimc-capture.c: