<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/arch/sparc/crypto, branch linux-3.19.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.19.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.19.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2014-12-02T14:55:48Z</updated>
<entry>
<title>crypto: sparc - replace memset by memzero_explicit</title>
<updated>2014-12-02T14:55:48Z</updated>
<author>
<name>Julia Lawall</name>
</author>
<published>2014-11-30T17:03:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8202cd720637e891639bf8e4af00d5431553c5b9'/>
<id>urn:sha1:8202cd720637e891639bf8e4af00d5431553c5b9</id>
<content type='text'>
Memset on a local variable may be removed when it is called just before the
variable goes out of scope.  Using memzero_explicit defeats this
optimization.  A simplified version of the semantic patch that makes this
change is as follows: (http://coccinelle.lip6.fr/)

// &lt;smpl&gt;
@@
identifier x;
type T;
@@

{
... when any
T x[...];
... when any
    when exists
- memset
+ memzero_explicit
  (x,
-0,
  ...)
... when != x
    when strict
}
// &lt;/smpl&gt;

This change was suggested by Daniel Borkmann &lt;dborkman@redhat.com&gt;

Signed-off-by: Julia Lawall &lt;Julia.Lawall@lip6.fr&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
<entry>
<title>crypto: prefix module autoloading with "crypto-"</title>
<updated>2014-11-24T14:43:57Z</updated>
<author>
<name>Kees Cook</name>
</author>
<published>2014-11-21T01:05:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5d26a105b5a73e5635eae0629b42fa0a90e07b7b'/>
<id>urn:sha1:5d26a105b5a73e5635eae0629b42fa0a90e07b7b</id>
<content type='text'>
This prefixes all crypto module loading with "crypto-" so we never run
the risk of exposing module auto-loading to userspace via a crypto API,
as demonstrated by Mathias Krause:

https://lkml.org/lkml/2013/3/4/70

Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
</entry>
<entry>
<title>sparc64: fix sparse warnings in aes_glue.c</title>
<updated>2014-05-19T02:01:33Z</updated>
<author>
<name>Sam Ravnborg</name>
</author>
<published>2014-05-16T21:26:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=756382cb5743b8f5c8383672928f0bd955d82a7a'/>
<id>urn:sha1:756382cb5743b8f5c8383672928f0bd955d82a7a</id>
<content type='text'>
Fix following warnings:
aes_glue.c:127:16: warning: symbol 'aes128_ops' was not declared. Should it be static?
aes_glue.c:139:16: warning: symbol 'aes192_ops' was not declared. Should it be static?
aes_glue.c:151:16: warning: symbol 'aes256_ops' was not declared. Should it be static?

Fix by defining the variables static as they are not used outside this file

Signed-off-by: Sam Ravnborg &lt;sam@ravnborg.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>sparc64: Set CRYPTO_TFM_REQ_MAY_SLEEP consistently in CAMELLIA code.</title>
<updated>2012-12-19T23:44:31Z</updated>
<author>
<name>David S. Miller</name>
</author>
<published>2012-12-19T23:44:31Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=62ba63dc892cf836ecb9ce4fdb7644d45c95070b'/>
<id>urn:sha1:62ba63dc892cf836ecb9ce4fdb7644d45c95070b</id>
<content type='text'>
We use the FPU and therefore cannot sleep during the crypto
loops.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>sparc64: Set CRYPTO_TFM_REQ_MAY_SLEEP consistently in DES code.</title>
<updated>2012-12-19T23:43:38Z</updated>
<author>
<name>David S. Miller</name>
</author>
<published>2012-12-19T23:43:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b3a37947074fa0a488d6c7ede58125b2278ab4e8'/>
<id>urn:sha1:b3a37947074fa0a488d6c7ede58125b2278ab4e8</id>
<content type='text'>
We use the FPU and therefore cannot sleep during the crypto
loops.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>sparc64: Fix ECB looping constructs in AES code.</title>
<updated>2012-12-19T23:30:07Z</updated>
<author>
<name>David S. Miller</name>
</author>
<published>2012-12-19T23:30:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ce6889515d5d481a5bd8ce5913dfed18f08310ea'/>
<id>urn:sha1:ce6889515d5d481a5bd8ce5913dfed18f08310ea</id>
<content type='text'>
Things works better when you increment the source buffer pointer
properly.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>sparc64: Set CRYPTO_TFM_REQ_MAY_SLEEP consistently in AES code.</title>
<updated>2012-12-19T23:22:03Z</updated>
<author>
<name>David S. Miller</name>
</author>
<published>2012-12-19T23:22:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b35d282ef7345320b594d48d8d70caedfa962a01'/>
<id>urn:sha1:b35d282ef7345320b594d48d8d70caedfa962a01</id>
<content type='text'>
We use the FPU and therefore cannot sleep during the crypto
loops.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>sparc64: Fix AES ctr mode block size.</title>
<updated>2012-12-19T23:20:23Z</updated>
<author>
<name>David S. Miller</name>
</author>
<published>2012-12-19T23:20:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a8d97cef2168ffe5af1aeed6bf6cdc3ce53f3d0b'/>
<id>urn:sha1:a8d97cef2168ffe5af1aeed6bf6cdc3ce53f3d0b</id>
<content type='text'>
Like the generic versions, we need to support a block size
of '1' for CTR mode AES.

This was discovered thanks to all of the new test cases added by
Jussi Kivilinna.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>sparc64: Fix unrolled AES 256-bit key loops.</title>
<updated>2012-12-19T23:19:11Z</updated>
<author>
<name>David S. Miller</name>
</author>
<published>2012-12-19T23:19:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9f28ffc03e93343ac04874fda9edb7affea45165'/>
<id>urn:sha1:9f28ffc03e93343ac04874fda9edb7affea45165</id>
<content type='text'>
The basic scheme of the block mode assembler is that we start by
enabling the FPU, loading the key into the floating point registers,
then iterate calling the encrypt/decrypt routine for each block.

For the 256-bit key cases, we run short on registers in the unrolled
loops.

So the {ENCRYPT,DECRYPT}_256_2() macros reload the key registers that
get clobbered.

The unrolled macros, {ENCRYPT,DECRYPT}_256(), are not mindful of this.

So if we have a mix of multi-block and single-block calls, the
single-block unrolled 256-bit encrypt/decrypt can run with some
of the key registers clobbered.

Handle this by always explicitly loading those registers before using
the non-unrolled 256-bit macro.

This was discovered thanks to all of the new test cases added by
Jussi Kivilinna.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>sparc64: Fix build with mix of modular vs. non-modular crypto drivers.</title>
<updated>2012-11-10T04:55:16Z</updated>
<author>
<name>David S. Miller</name>
</author>
<published>2012-11-10T04:53:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=226f7cea949303a3e1911999a9a2c71b0a708e73'/>
<id>urn:sha1:226f7cea949303a3e1911999a9a2c71b0a708e73</id>
<content type='text'>
We tried linking in a single built object to hold the device table,
but only works if all of the sparc64 crypto modules get built the same
way (modular vs. non-modular).

Just include the device ID stub into each driver source file so that
the table gets compiled into the correct result in all cases.

Reported-by: Meelis Roos &lt;mroos@linux.ee&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
