- 11 Jul, 2012 3 commits
-
-
Milan Broz authored
kfree(new_key_mem) in rfc4106_set_key() should be called on malloced pointer, not on aligned one, otherwise it can cause invalid pointer on free. (Seen at least once when running tcrypt tests with debug kernel.) Signed-off-by:
Milan Broz <mbroz@redhat.com> Signed-off-by:
Herbert Xu <herbert@gondor.apana.org.au>
-
Alex Porosanu authored
This patch adds support for retrieving and printing of SEC ERA information. It is useful for knowing beforehand what features exist from the SEC point of view on a certain SoC. Only era-s 1 to 4 are currently supported; other eras will appear as unknown. Signed-off-by:
Alex Porosanu <alexandru.porosanu@freescale.com> - rebased onto current cryptodev master - made caam_eras static Signed-off-by:
Kim Phillips <kim.phillips@freescale.com> Signed-off-by:
-
Bharat Bhushan authored
The caam job rings (input/output job ring) are allocated using dma_map_single(). These job rings can be visualized as the ring buffers in which the jobs are en-queued/de-queued. The s/w enqueues the jobs in input job ring which h/w dequeues and after processing it copies the jobs in output job ring. Software then de-queues the job from output ring. Using dma_map/unmap_single() is not preferred way to allocate memory for this type of requirements because this adds un-necessary complexity. Example, if bounce buffer (SWIOTLB) will get used then to make any change visible in this memory to other processing unit requires dmap_unmap_single() or dma_sync_single_for_cpu/device(). The dma_unmap_single() can not be used as this will free the bounce buffer, this will require changing the job rings on running system and I seriously doubt that it will be not possible or very complex to implement. Also using dma_sync_single_for_cpu/device() will also add unnecessary complexity. The simple and preferred way is using dma_alloc_coherent() for these type of memory requirements. This resolves the Linux boot crash issue when "swiotlb=force" is set in bootargs on systems which have memory more than 4G. Signed-off-by:
Bharat Bhushan <bharat.bhushan@freescale.com> Acked-by:
-
- 27 Jun, 2012 36 commits
-
-
Steffen Klassert authored
git commit 39871037 (crypto: algapi - Move larval completion into algboss) replaced accidentally a call to complete_all() by a call to complete(). This causes a hang on crypto allocation if we have more than one larval waiter. This pach restores the call to complete_all(). Signed-off-by:
Steffen Klassert <steffen.klassert@secunet.com> Signed-off-by:
-
Sebastian Andrzej Siewior authored
Since commit ce6dd368 ("crypto: arc4 - improve performance by adding ecb(arc4)) we need to pull in a blkcipher. |ERROR: "crypto_blkcipher_type" [crypto/arc4.ko] undefined! |ERROR: "blkcipher_walk_done" [crypto/arc4.ko] undefined! |ERROR: "blkcipher_walk_virt" [crypto/arc4.ko] undefined! Signed-off-by:
Sebastian Andrzej Siewior <sebastian@breakpoint.cc> Signed-off-by:
-
Kim Phillips authored
there is no noticeable benefit for multiple cores to process one job ring's output ring: in fact, we can benefit from cache effects of having the back-half stay on the core that receives a particular ring's interrupts, and further relax general contention and the locking involved with reading outring_used, since tasklets run atomically. Signed-off-by:
-
Kim Phillips authored
Memory barriers are implied by the i/o register write implementation (at least on Power). So we can remove the redundant wmb() in caam_jr_enqueue, and, in dequeue(), hoist the h/w done notification write up to before we need to increment the head of the ring, and save an smp_mb. Signed-off-by:
-
Kim Phillips authored
Code was needlessly checking the s/w job ring when there would be nothing to process if the h/w's output completion ring were empty anyway. Signed-off-by:
-
Kim Phillips authored
The enqueue lock isn't used in any interrupt context, and the dequeue lock isn't used in the h/w interrupt context, only in bh context. Signed-off-by:
-
Kim Phillips authored
It has been observed that in zero-loss benchmarks, when a slow traffic rate is being tested, the IRQ timer coalescing parameter was set too high, and the ethernet controller would start dropping packets because the job ring back half wouldn't be executed in time before the ethernet controller would fill its buffers, thereby significantly reducing the zero-loss performance figures. Empirical testing has shown that the best zero-loss performance is achieved when IRQ coalescing is set to minimum values and/or turned off, since apparently the job ring driver already implements an adequately-performing general-purpose IRQ mitigation strategy in software. Whilst we could go with minimal count (2-8) and timing settings (192-256), we prefer just turning h/w coalescing altogether off to minimize setkey latency (due to split key generation), and for consistent cross-SoC performance (the SEC vs. core clock ratio changes). Signed-off-by:
-
Kim Phillips authored
The SEC v4.x' RNGB h/w block self-initialized. RNG4, available on SEC versions 5 and beyond, is based on a different standard that requires manual initialization. Also update any new errors From the SEC v5.2 reference manual: The SEC v5.2's RNG4 unit reuses some error IDs, thus the addition of rng_err_id_list over the CHA-independent err_id_list. Signed-off-by:
-
Kim Phillips authored
SEC v4.x were only 36-bit, SEC v5+ are 40-bit capable. Also set a DMA mask for any job ring devices created. Signed-off-by:
-
Yuan Kang authored
caam_read copies random bytes from two buffers into output. caam rng can fill empty buffer 0xffff bytes at a time, but the buffer sizes are rounded down to multiple of cacheline size. Signed-off-by:
Yuan Kang <Yuan.Kang@freescale.com> Signed-off-by:
-
Yuan Kang authored
support chained scatterlists for aead, ablkcipher and ahash. Signed-off-by:
Kudupudi Ugendreshwar <B38865@freescale.com> Signed-off-by:
-
Yuan Kang authored
caam supports and registers unkeyed sha algorithms and md5. Signed-off-by:
-
Yuan Kang authored
caam supports ahash hmac with sha algorithms and md5. Signed-off-by:
-
Yuan Kang authored
- rename scatterlist and link_tbl functions - link_tbl changed to sec4_sg - sg_to_link_tbl_one changed to dma_to_sec4_sg_one, since no scatterlist is use Signed-off-by:
-
Yuan Kang authored
create separate files for split key generation and scatterlist functions. Signed-off-by:
-
Yuan Kang authored
remove caam_jr_register and caam_jr_deregister to allow sharing of job rings. Signed-off-by:
-
Yuan Kang authored
functions for external storage of seq in/out lengths, i.e., for 32-bit lengths. These type-dependent functions automatically determine whether to store the length internally (embedded in the command header word) or externally (after the address pointer), based on size of the type given. Signed-off-by:
-
Hemant Agrawal authored
Add a PDB header file to support building protocol descriptors. Signed-off-by:
Steve Cornelius <sec@pobox.com> Signed-off-by:
Hemant Agrawal <hemant@freescale.com> Signed-off-by:
-
Kim Phillips authored
init_desc, by always ORing with 1 for the descriptor header inclusion into the descriptor length, and init_sh_desc_pdb, by always specifying the descriptor length modification for the PDB via options, would not allow for odd length PDBs to be embedded in the constructed descriptor length. Fix this by simply changing the OR to an addition. also round-up pdb_bytes to the next SEC command unit size, to allow for, e.g., optional packet header bytes that aren't a multiple of CAAM_CMD_SZ. Reported-by:
Radu-Andrei BULIE <radu.bulie@freescale.com> Signed-off-by:
-
Yashpal Dutta authored
In case of protocol acceleration descriptors, Shared descriptor header must carry size of header length + PDB length in words which will be skipped by DECO while processing descriptor to provide first command word offset Signed-off-by:
Yashpal Dutta <yashpal.dutta@freescale.com> Signed-off-by:
-
Kim Phillips authored
SEC4 h/w gets configured in 32- vs. 36-bit physical addressing modes depending on the size of dma_addr_t, which is not always equal to sizeof(u32 *). Also fixed alignment of a dma_unmap call whilst in there. Signed-off-by:
-
Kim Phillips authored
presumably leftovers from possible macro development. Signed-off-by:
-
Jussi Kivilinna authored
Move AES header to the new asm/crypto directory. Signed-off-by:
Jussi Kivilinna <jussi.kivilinna@mbnet.fi> Signed-off-by:
-
Jussi Kivilinna authored
Move serpent crypto headers to the new asm/crypto/ directory. Signed-off-by:
-
Jussi Kivilinna authored
Now that shared glue code is available, convert twofish-avx to use it. Cc: Johannes Goetzfried <Johannes.Goetzfried@informatik.stud.uni-erlangen.de> Signed-off-by:
-
Jussi Kivilinna authored
Now that shared glue code is available, convert twofish-x86_64-3way to use it. Signed-off-by:
-
Jussi Kivilinna authored
Now that shared glue code is available, convert camellia-x86_64 to use it. Signed-off-by:
-
Jussi Kivilinna authored
Now that shared glue code is available, convert serpent-avx to use it. Cc: Johannes Goetzfried <Johannes.Goetzfried@informatik.stud.uni-erlangen.de> Signed-off-by:
-
Jussi Kivilinna authored
Now that serpent-sse2 glue code has been made generic, it can be split to separate module. Signed-off-by:
-
Jussi Kivilinna authored
crypto: serpent-sse2 - prepare serpent-sse2 glue code into generic x86 glue code for 128bit block ciphers Block cipher implementations in arch/x86/crypto/ contain common glue code that is currently duplicated in each module (camellia-x86_64, twofish-x86_64-3way, twofish-avx, serpent-sse2 and serpent-avx). This patch prepares serpent-sse2 glue into generic glue code for all 128bit block ciphers to use in arch/x86/crypto. Signed-off-by:
-
Jussi Kivilinna authored
Remove duplicate ablk_* functions and make use of ablk_helper module instead. Signed-off-by:
-
Jussi Kivilinna authored
Remove duplicate ablk_* functions and make use of ablk_helper module instead. Signed-off-by:
-
Jussi Kivilinna authored
Move ablk-* functions to separate module to share common code between cipher implementations. Signed-off-by:
-
Seth Jennings authored
Signed-off-by:
Seth Jennings <sjenning@linux.vnet.ibm.com> Acked-by:
Kent Yoder <key@linux.vnet.ibm.com> Signed-off-by:
-
Seth Jennings authored
When the nx driver was pulled, the Makefile that actually builds it is arch/powerpc/Makefile. This is unnatural. This patch moves the line that builds the nx driver from arch/powerpc/Makefile to drivers/crypto/Makefile where it belongs. Signed-off-by:
-
Benoît Thébaudeau authored
Commit 45001e92, which added support for RNGA, ignored the previous commit 984e976f, which changed the data_present API. Cc: Matt Mackall <mpm@selenic.com> Cc: Sascha Hauer <kernel@pengutronix.de> Cc: Alan Carvalho de Assis <acassis@gmail.com> Cc: <linux-arm-kernel@lists.infradead.org> Signed-off-by:
Benoît Thébaudeau <benoit.thebaudeau@advansee.com> Signed-off-by:
-
- 22 Jun, 2012 1 commit
-
-
Herbert Xu authored
It has been observed that sometimes the crypto allocation code will get stuck for 60 seconds or multiples thereof. This is usually caused by an algorithm failing to pass the self-test. If an algorithm fails to be constructed, we will immediately notify all larval waiters. However, if it succeeds in construction, but then fails the self-test, we won't notify anyone at all. This patch fixes this by merging the notification in the case where the algorithm fails to be constructed with that of the the case where it pases the self-test. This way regardless of what happens, we'll give the larval waiters an answer. Signed-off-by:
-
