<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux-stable.git/drivers/crypto/rockchip, branch linux-4.8.y</title>
<subtitle>Linux kernel stable tree</subtitle>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/'/>
<entry>
<title>crypto: rockchip - add hash support for crypto engine in rk3288</title>
<updated>2016-02-27T19:26:29+00:00</updated>
<author>
<name>Zain Wang</name>
<email>zain.wang@rock-chips.com</email>
</author>
<published>2016-02-16T02:15:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=bfd927ffa219ac81082b2dcc61a1c4037869befc'/>
<id>bfd927ffa219ac81082b2dcc61a1c4037869befc</id>
<content type='text'>
Add md5 sha1 sha256 support for crypto engine in rk3288.

Signed-off-by: Zain Wang &lt;zain.wang@rock-chips.com&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add md5 sha1 sha256 support for crypto engine in rk3288.

Signed-off-by: Zain Wang &lt;zain.wang@rock-chips.com&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>crypto: rockchip - fix possible deadlock</title>
<updated>2015-12-04T14:21:48+00:00</updated>
<author>
<name>Heiko Stuebner</name>
<email>heiko@sntech.de</email>
</author>
<published>2015-11-28T12:27:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=ac7c8e6b6dc959d285382c7e9cdfe608205f0c68'/>
<id>ac7c8e6b6dc959d285382c7e9cdfe608205f0c68</id>
<content type='text'>
Lockdep warns about a possible deadlock resulting from the use of regular
spin_locks:

=================================
[ INFO: inconsistent lock state ]
4.4.0-rc2+ #2724 Not tainted
---------------------------------
inconsistent {SOFTIRQ-ON-W} -&gt; {IN-SOFTIRQ-W} usage.
ksoftirqd/0/3 [HC0[0]:SC1[1]:HE1:SE0] takes:
(&amp;(&amp;crypto_info-&gt;lock)-&gt;rlock){+.?...}, at: [&lt;bf14a65c&gt;] rk_crypto_tasklet_cb+0x24/0xb4 [rk_crypto]
{SOFTIRQ-ON-W} state was registered at:
  [&lt;c007f4ac&gt;] lock_acquire+0x178/0x218
  [&lt;c0759bac&gt;] _raw_spin_lock+0x54/0x64
  [&lt;bf14af88&gt;] rk_handle_req+0x7c/0xbc [rk_crypto]
  [&lt;bf14b040&gt;] rk_des_ecb_encrypt+0x2c/0x30 [rk_crypto]
  [&lt;bf14b05c&gt;] rk_aes_ecb_encrypt+0x18/0x1c [rk_crypto]
  [&lt;c028c820&gt;] skcipher_encrypt_ablkcipher+0x64/0x68
  [&lt;c0290770&gt;] __test_skcipher+0x2a8/0x8dc
  [&lt;c0292e94&gt;] test_skcipher+0x38/0xc4
  [&lt;c0292fb0&gt;] alg_test_skcipher+0x90/0xb0
  [&lt;c0292158&gt;] alg_test+0x1e8/0x280
  [&lt;c028f6f4&gt;] cryptomgr_test+0x34/0x54
  [&lt;c004bbe8&gt;] kthread+0xf4/0x10c
  [&lt;c0010010&gt;] ret_from_fork+0x14/0x24
irq event stamp: 10672
hardirqs last  enabled at (10672): [&lt;c002fac8&gt;] tasklet_action+0x48/0x104
hardirqs last disabled at (10671): [&lt;c002faa0&gt;] tasklet_action+0x20/0x104
softirqs last  enabled at (10658): [&lt;c002ef84&gt;] __do_softirq+0x358/0x49c
softirqs last disabled at (10669): [&lt;c002f108&gt;] run_ksoftirqd+0x40/0x80

other info that might help us debug this:
Possible unsafe locking scenario:

    CPU0
    ----
  lock(&amp;(&amp;crypto_info-&gt;lock)-&gt;rlock);
  &lt;Interrupt&gt;
    lock(&amp;(&amp;crypto_info-&gt;lock)-&gt;rlock);

 *** DEADLOCK ***

Fix this by moving to irq-disabling spinlocks.

Signed-off-by: Heiko Stuebner &lt;heiko@sntech.de&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Lockdep warns about a possible deadlock resulting from the use of regular
spin_locks:

=================================
[ INFO: inconsistent lock state ]
4.4.0-rc2+ #2724 Not tainted
---------------------------------
inconsistent {SOFTIRQ-ON-W} -&gt; {IN-SOFTIRQ-W} usage.
ksoftirqd/0/3 [HC0[0]:SC1[1]:HE1:SE0] takes:
(&amp;(&amp;crypto_info-&gt;lock)-&gt;rlock){+.?...}, at: [&lt;bf14a65c&gt;] rk_crypto_tasklet_cb+0x24/0xb4 [rk_crypto]
{SOFTIRQ-ON-W} state was registered at:
  [&lt;c007f4ac&gt;] lock_acquire+0x178/0x218
  [&lt;c0759bac&gt;] _raw_spin_lock+0x54/0x64
  [&lt;bf14af88&gt;] rk_handle_req+0x7c/0xbc [rk_crypto]
  [&lt;bf14b040&gt;] rk_des_ecb_encrypt+0x2c/0x30 [rk_crypto]
  [&lt;bf14b05c&gt;] rk_aes_ecb_encrypt+0x18/0x1c [rk_crypto]
  [&lt;c028c820&gt;] skcipher_encrypt_ablkcipher+0x64/0x68
  [&lt;c0290770&gt;] __test_skcipher+0x2a8/0x8dc
  [&lt;c0292e94&gt;] test_skcipher+0x38/0xc4
  [&lt;c0292fb0&gt;] alg_test_skcipher+0x90/0xb0
  [&lt;c0292158&gt;] alg_test+0x1e8/0x280
  [&lt;c028f6f4&gt;] cryptomgr_test+0x34/0x54
  [&lt;c004bbe8&gt;] kthread+0xf4/0x10c
  [&lt;c0010010&gt;] ret_from_fork+0x14/0x24
irq event stamp: 10672
hardirqs last  enabled at (10672): [&lt;c002fac8&gt;] tasklet_action+0x48/0x104
hardirqs last disabled at (10671): [&lt;c002faa0&gt;] tasklet_action+0x20/0x104
softirqs last  enabled at (10658): [&lt;c002ef84&gt;] __do_softirq+0x358/0x49c
softirqs last disabled at (10669): [&lt;c002f108&gt;] run_ksoftirqd+0x40/0x80

other info that might help us debug this:
Possible unsafe locking scenario:

    CPU0
    ----
  lock(&amp;(&amp;crypto_info-&gt;lock)-&gt;rlock);
  &lt;Interrupt&gt;
    lock(&amp;(&amp;crypto_info-&gt;lock)-&gt;rlock);

 *** DEADLOCK ***

Fix this by moving to irq-disabling spinlocks.

Signed-off-by: Heiko Stuebner &lt;heiko@sntech.de&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>crypto: rockchip - add crypto driver for rk3288</title>
<updated>2015-11-27T13:19:32+00:00</updated>
<author>
<name>Zain Wang</name>
<email>zain.wang@rock-chips.com</email>
</author>
<published>2015-11-25T05:43:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux-stable.git/commit/?id=433cd2c617bfbac27a02e40fbcce1713c84ce441'/>
<id>433cd2c617bfbac27a02e40fbcce1713c84ce441</id>
<content type='text'>
Crypto driver support:
     ecb(aes) cbc(aes) ecb(des) cbc(des) ecb(des3_ede) cbc(des3_ede)
You can alloc tags above in your case.

And other algorithms and platforms will be added later on.

Signed-off-by: Zain Wang &lt;zain.wang@rock-chips.com&gt;
Tested-by: Heiko Stuebner &lt;heiko@sntech.de&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Crypto driver support:
     ecb(aes) cbc(aes) ecb(des) cbc(des) ecb(des3_ede) cbc(des3_ede)
You can alloc tags above in your case.

And other algorithms and platforms will be added later on.

Signed-off-by: Zain Wang &lt;zain.wang@rock-chips.com&gt;
Tested-by: Heiko Stuebner &lt;heiko@sntech.de&gt;
Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
</pre>
</div>
</content>
</entry>
</feed>
