<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi">
    <title>gmane.linux.kernel.cryptoapi</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8929"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8926"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8925"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8923"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8922"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8921"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8919"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8918"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8916"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8915"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8913"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8912"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8911"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8909"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8908"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8907"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8905"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8903"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8902"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8894"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8929">
    <title>Re: Oops on 3.10-rc1 related to ssh256_ssse3</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8929</link>
    <description>&lt;pre&gt;
Appears to be stack corruption caused by sha256_transform_ssse3. Does attached patch help?

-Jussi


&lt;/pre&gt;</description>
    <dc:creator>Jussi Kivilinna</dc:creator>
    <dc:date>2013-05-20T20:15:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8926">
    <title>Re: [PATCH 19/39] ARM: ux500: Register Cyrp and Hash platform drivers on Snowball</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8926</link>
    <description>&lt;pre&gt;

Patch applied now that the deps are in place.

Yours,
Linus Walleij
&lt;/pre&gt;</description>
    <dc:creator>Linus Walleij</dc:creator>
    <dc:date>2013-05-20T12:17:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8925">
    <title>Re: [PATCH 18/39] crypto: ux500/[cryp|hash] - Show successful start-up in the bootlog</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8925</link>
    <description>&lt;pre&gt;

Patch applied with Herbert's ACK.

Thanks,
Linus Walleij
&lt;/pre&gt;</description>
    <dc:creator>Linus Walleij</dc:creator>
    <dc:date>2013-05-20T12:15:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8923">
    <title>Re: [PATCH 16/39] crypto: ux500/cryp - Set DMA configuration though dma_slave_config()</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8923</link>
    <description>&lt;pre&gt;

Patch applied with Herbert's ACK.

Thanks,
Linus Walleij
&lt;/pre&gt;</description>
    <dc:creator>Linus Walleij</dc:creator>
    <dc:date>2013-05-20T12:12:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8922">
    <title>Re: [PATCH 15/39] crypto: ux500/cryp - Prepare clock before enabling it</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8922</link>
    <description>&lt;pre&gt;

Patch applied with Herbert's ACK.

Yours,
Linus Walleij
&lt;/pre&gt;</description>
    <dc:creator>Linus Walleij</dc:creator>
    <dc:date>2013-05-20T12:10:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8921">
    <title>Re: [PATCH 14/39] ARM: ux500: Stop passing Hash DMA channel config information though pdata</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8921</link>
    <description>&lt;pre&gt;

Patch applied now that the deps are in!

Yours,
Linus Walleij
&lt;/pre&gt;</description>
    <dc:creator>Linus Walleij</dc:creator>
    <dc:date>2013-05-20T12:09:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8919">
    <title>Re: [PATCH 12/39] crypto: ux500/hash - Prepare clock before enabling it</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8919</link>
    <description>&lt;pre&gt;

Patch applied to my dma40 branch with Herbert's ACK.

Yours,
Linus Walleij
&lt;/pre&gt;</description>
    <dc:creator>Linus Walleij</dc:creator>
    <dc:date>2013-05-20T12:05:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8918">
    <title>Re: [PATCH 02/39] dmaengine: ste_dma40: Remove unnecessary call to d40_phy_cfg()</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8918</link>
    <description>&lt;pre&gt;
I've fixed it up!

Yours,
Linus Walleij
&lt;/pre&gt;</description>
    <dc:creator>Linus Walleij</dc:creator>
    <dc:date>2013-05-20T12:01:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8916">
    <title>NIST SP800-138 availibility using kernel crypto APIs for SMB3.0 MAC generation</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8916</link>
    <description>&lt;pre&gt;With the recent patches added to kernel crypto for improving AES
support, adding aesni etc, it seems like it is time to add AES CMAC
to the cifs kernel module (for the popular SMB3 signing and per-share
encryption) but needed for an implementation for SP800-138 in kernel
crypto codebase.
Was specifically interested using the way defined in 3.1.4.2 of
MS-SMB2 document, in particular

KDF in Counter mode (section 5.1 of NIST SP 800-108) or a way to specify a mode
PRF as HMAC-SHA256 (or a way to specify a PRF)


cifs client would use this algorithm for SMB3.0 MAC generation
(network packet signing on network file system mounts to newer
generation NAS, and Windows 2012) and also for per-share encryption
(which is also available on the most recent generation of NAS via
SMB3). Apparently with current Intel processors having hardware for
this kind of encryption offload - full packet encryption is faster
than packet signing used to be (with the older standard algorithms)
and just doing packet signing is really fast.&lt;/pre&gt;</description>
    <dc:creator>Shirish Pargaonkar</dc:creator>
    <dc:date>2013-05-20T02:49:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8915">
    <title>[PATCH v2 1/1] crypto: Added support for Freescale's DCP co-processor</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8915</link>
    <description>&lt;pre&gt;This patch enables the DCP crypto functionality on imx28.
Currently, only aes-128-cbc is supported.
Moreover, the dcpboot misc-device, which is used by Freescale's
SDK tools and uses a non-software-readable OTP-key, is added.

Changes of v2:
- ring buffer for hardware-descriptors
- use of ablkcipher walk
- OTP key encryption/decryption via misc-device
  (compatible to Freescale-SDK)
- overall cleanup

The DCP is also capable of sha1/sha256 but I won't be able to add 
that anytime soon.
Tested with built-in runtime-self-test, tcrypt and openssl via 
cryptodev 1.6 on imx28-evk and a custom built imx28-board.


Signed-off-by: Tobias Rauter &amp;lt;tobias.rauter&amp;lt; at &amp;gt;gmail.com&amp;gt;
---
 arch/arm/boot/dts/imx28.dtsi |   2 +-
 drivers/crypto/Kconfig       |  10 +
 drivers/crypto/Makefile      |   1 +
 drivers/crypto/dcp.c         | 925 +++++++++++++++++++++++++++++++++++++++++++
 4 files changed, 937 insertions(+), 1 deletion(-)
 create mode 100644 drivers/crypto/dcp.c

diff --git a/arch/arm/boot/dts/imx28.dtsi b/arch/arm/boot/dt&lt;/pre&gt;</description>
    <dc:creator>Tobias Rauter</dc:creator>
    <dc:date>2013-05-19T19:59:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8913">
    <title>Re: [PATCH 20/39] usb: musb: ux500: move channel number knowledge into the driver</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8913</link>
    <description>&lt;pre&gt;On Wed, May 15, 2013 at 10:14 PM, Fabio Baltieri
&amp;lt;fabio.baltieri&amp;lt; at &amp;gt;linaro.org&amp;gt; wrote:

OK so Felipe can merge these smallish patches to musb, fine...

The other (DMA) stuff needs to be merged together with the rest
of the DMA40 series, so here basically Felipe needs an indication
if he can ACK it so I merge it through ARM SoC without colissions
and it sounds like we can make the assumption that this will work.

Yours,
Linus Walleij
&lt;/pre&gt;</description>
    <dc:creator>Linus Walleij</dc:creator>
    <dc:date>2013-05-17T06:35:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8912">
    <title>Re: linux-next: Tree for May 15 (crypto /crct10dif)</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8912</link>
    <description>&lt;pre&gt;2013/5/17 Tim Chen &amp;lt;tim.c.chen&amp;lt; at &amp;gt;linux.intel.com&amp;gt;:

cool.

&lt;/pre&gt;</description>
    <dc:creator>Xiong Zhou</dc:creator>
    <dc:date>2013-05-17T03:09:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8911">
    <title>Re: linux-next: Tree for May 15 (crypto /crct10dif)</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8911</link>
    <description>&lt;pre&gt;2013/5/16 Geert Uytterhoeven &amp;lt;geert&amp;lt; at &amp;gt;linux-m68k.org&amp;gt;:

En.. make sense, Thanks.

Xiong

&lt;/pre&gt;</description>
    <dc:creator>Xiong Zhou</dc:creator>
    <dc:date>2013-05-17T03:06:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8909">
    <title>Re: linux-next: Tree for May 15 (crypto /crct10dif)</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8909</link>
    <description>&lt;pre&gt;
This is the fix I think that will resolve the build issues.  The generic
crc-t10dif transform depends on the library function crc_t10dif_generic
in lib/crc-t10dif.c, so "depends on CRC_T10DIF" for CRYPTO_CRCT10DIF is
needed.

Now for CRC_T10DIF, we should use select CRYPTO_HASH, so it can try to
allocate a T10DIF transform if it is available.  If not, it will simply
use the crc_t10dif_generic function. Loading the
generic t10dif crypto transform is not mandatory for the library
function crc_t10dif. 

Thanks for catching the issues.

Tim

Signed-off-by: Tim Chen &amp;lt;tim.c.chen&amp;lt; at &amp;gt;linux.intel.com&amp;gt;
---
diff --git a/crypto/Kconfig b/crypto/Kconfig
index d1ca631..015df24 100644
--- a/crypto/Kconfig
+++ b/crypto/Kconfig
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -379,6 +379,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; config CRYPTO_CRC32_PCLMUL
 config CRYPTO_CRCT10DIF
 tristate "CRCT10DIF algorithm"
 select CRYPTO_HASH
+depends on CRC_T10DIF
 help
   CRC T10 Data Integrity Field computation is being cast as
   a crypto transform.  This allows for faster crc t10 diff
diff --git a/lib/Kconfig&lt;/pre&gt;</description>
    <dc:creator>Tim Chen</dc:creator>
    <dc:date>2013-05-16T16:59:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8908">
    <title>Re: linux-next: Tree for May 15 (crypto /crct10dif)</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8908</link>
    <description>&lt;pre&gt;
I think "depends on" CRC_T10DIF is okay.  This generic transform is not
needed if we are not using the T10-DIF library.  It is meant for
wrapping the library call to t10-dif as a crypto transform.



&lt;/pre&gt;</description>
    <dc:creator>Tim Chen</dc:creator>
    <dc:date>2013-05-16T16:09:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8907">
    <title>Oops on 3.10-rc1 related to ssh256_ssse3</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8907</link>
    <description>&lt;pre&gt;Hello,

I have an encrypted disc (dm-crypt, type LUKS1, ssh256 as hash
algorithm). I have an Intel Core i5 M450 that supports ssse3. Find
below the output from netconsole with the oops. The last warning
appeared when I restart the pc using the magic sysrq key combination
REISUB. I have the same problem with a different laptop with an AMD
E-450 APU.

If you need further information, feel free to ask.


Best regards,
Julian Wollrath

[    3.647071] device-mapper: uevent: version 1.0.3
[    3.647245] device-mapper: ioctl: 4.24.0-ioctl (2013-01-15) initialised: dm-devel&amp;lt; at &amp;gt;redhat.com
[   11.619603] sha256_ssse3: Using SSSE3 optimized SHA-256 implementation
[   12.131483] BUG: unable to handle kernel paging request at ffff8800bb593000
[   12.131848] IP: [&amp;lt;ffffffffa016b083&amp;gt;] loop0+0x27/0x44 [sha256_ssse3]
[   12.132032] PGD 1a32067 PUD 1a35067 PMD 1a36067 PTE 0
[   12.132427] Oops: 0000 [#1] SMP 
[   12.132670] Modules linked in: sha256_ssse3(+) sha256_generic twofish_generic twofish_x86_64_3way xts lrw gf128mul glue&lt;/pre&gt;</description>
    <dc:creator>Julian Wollrath</dc:creator>
    <dc:date>2013-05-16T13:41:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8905">
    <title>[PATCH 6/6] crypto: ux500/hash - Enable DT probing of the driver</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8905</link>
    <description>&lt;pre&gt;By providing an OF match table with a suitable compatible string, we
can ensure the ux500-hasht driver is probed by supplying an associated
DT node in a given platform's Device Tree.

Cc: Herbert Xu &amp;lt;herbert&amp;lt; at &amp;gt;gondor.apana.org.au&amp;gt;
Cc: linux-crypto&amp;lt; at &amp;gt;vger.kernel.org
Signed-off-by: Lee Jones &amp;lt;lee.jones&amp;lt; at &amp;gt;linaro.org&amp;gt;
---
 drivers/crypto/ux500/hash/hash_core.c |    6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/drivers/crypto/ux500/hash/hash_core.c b/drivers/crypto/ux500/hash/hash_core.c
index 9ca6fbb..f89fe8a 100644
--- a/drivers/crypto/ux500/hash/hash_core.c
+++ b/drivers/crypto/ux500/hash/hash_core.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -1981,6 +1981,11 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; static int ux500_hash_resume(struct device *dev)
 
 static SIMPLE_DEV_PM_OPS(ux500_hash_pm, ux500_hash_suspend, ux500_hash_resume);
 
+static const struct of_device_id ux500_hash_match[] = {
+        { .compatible = "stericsson,ux500-hash" },
+        { },
+};
+
 static struct platform_driver hash_driver = {
 .probe  = ux500_hash_probe,
 .remove = ux500_hash_remove,
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -1988,6 +1993,7 &lt;/pre&gt;</description>
    <dc:creator>Lee Jones</dc:creator>
    <dc:date>2013-05-16T11:27:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8903">
    <title>Re: [PATCH 34/39] dmaengine: ste_dma40: Convert data_width from register bit format to value</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8903</link>
    <description>&lt;pre&gt;Okay...

--
~Vinod
&lt;/pre&gt;</description>
    <dc:creator>Vinod Koul</dc:creator>
    <dc:date>2013-05-16T09:41:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8902">
    <title>Re: [PATCH 02/39] dmaengine: ste_dma40: Remove unnecessary call to d40_phy_cfg()</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8902</link>
    <description>&lt;pre&gt;Certainly not in MAINTAINERS file :)

--
~Vinod
&lt;/pre&gt;</description>
    <dc:creator>Vinod Koul</dc:creator>
    <dc:date>2013-05-16T09:40:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8894">
    <title>Re: [PATCH 08/39] dmaengine: ste_dma40: Remove redundant address fetching function</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8894</link>
    <description>&lt;pre&gt;Acked-by: Vinod Koul &amp;lt;vinod.koul&amp;lt; at &amp;gt;intel.com&amp;gt;

--
~Vinod
&lt;/pre&gt;</description>
    <dc:creator>Vinod Koul</dc:creator>
    <dc:date>2013-05-16T06:41:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8893">
    <title>Re: [PATCH 03/39] dmaengine: ste_dma40: Don't configure runtime configurable setup during allocate</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.cryptoapi/8893</link>
    <description>&lt;pre&gt;Acked-by: Vinod Koul &amp;lt;vinod.koul&amp;lt; at &amp;gt;intel.com&amp;gt;

--
~Vinod
&lt;/pre&gt;</description>
    <dc:creator>Vinod Koul</dc:creator>
    <dc:date>2013-05-16T06:36:40</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.linux.kernel.cryptoapi">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.linux.kernel.cryptoapi</link>
  </textinput>
</rdf:RDF>
