linux-toradex.git/crypto/ablkcipher.c, branch v3.2.3

crypto: algapi - Fix build problem with NET disabled

2011-11-10T22:57:06+00:00

The report functions use NLA_PUT so we need to ensure that NET
is enabled.

Reported-by: Luis Henriques 
Signed-off-by: Herbert Xu

crypto: Add userspace report for givcipher type algorithms

2011-10-21T12:24:05+00:00

Signed-off-by: Steffen Klassert 
Signed-off-by: Herbert Xu

crypto: Add userspace report for ablkcipher type algorithms

2011-10-21T12:24:05+00:00

Signed-off-by: Steffen Klassert 
Signed-off-by: Herbert Xu

crypto: skcipher - remove redundant NULL check

2011-01-29T04:09:43+00:00

Signed-off-by: Davidlohr Bueso 
Acked-by: David S. Miller 
Signed-off-by: Herbert Xu

crypto: skcipher - avoid NULL dereference

2010-06-23T10:01:45+00:00

Stanse found a potential NULL dereference in ablkcipher_next_slow.
Even though kmalloc fails, its retval is dereferenced later. Return
from that function properly earlier.

Signed-off-by: Jiri Slaby 
Acked-by: David S. Miller 
Signed-off-by: Herbert Xu

crypto: skcipher - Add ablkcipher_walk interfaces

2010-05-19T04:13:07+00:00

These are akin to the blkcipher_walk helpers.

The main differences in the async variant are:

1) Only physical walking is supported.  We can't hold on to
   kmap mappings across the async operation to support virtual
   ablkcipher_walk operations anyways.

2) Bounce buffers used for async more need to be persistent and
   freed at a later point in time when the async op completes.
   Therefore we maintain a list of writeback buffers and require
   that the ablkcipher_walk user call the 'complete' operation
   so we can copy the bounce buffers out to the real buffers and
   free up the bounce buffer chunks.

These interfaces will be used by the new Niagara2 crypto driver.

Signed-off-by: David S. Miller 
Signed-off-by: Herbert Xu

crypto: ablkcipher - Fix checkpatch errors

2010-02-16T12:23:37+00:00

Signed-off-by: Richard Hartmann 
Signed-off-by: Herbert Xu

crypto: blkcipher - Do not use eseqiv on stream ciphers

2009-08-14T12:58:18+00:00

Recently we switched to using eseqiv on SMP machines in preference
over chainiv.  However, eseqiv does not support stream ciphers so
they should still default to chainiv.

This patch applies the same check as done by eseqiv to weed out
the stream ciphers.  In particular, all algorithms where the IV
size is not equal to the block size will now default to chainiv.

Signed-off-by: Herbert Xu

crypto: skcipher - Change default sync geniv on SMP to eseqiv

2009-06-25T10:43:48+00:00

As it stands we use chainiv for sync algorithms and eseqiv for
async algorithms.  However, when there is more than one CPU
chainiv forces all processing to be serialised which is usually
not what you want.  Also, the added overhead of eseqiv isn't that
great.

Therefore this patch changes the default sync geniv on SMP machines
to eseqiv.  For the odd situation where the overhead is unacceptable
then chainiv is still available as an option.

Note that on UP machines chainiv is still preferred over eseqiv
for sync algorithms.

Signed-off-by: Herbert Xu

crypto: skcipher - Fix request for sync algorithms

2009-06-25T06:46:31+00:00

When a sync givcipher algorithm is requested, if an async version
of the same algorithm already exists, then we will loop forever
without ever constructing the sync version based on a blkcipher.

This is because we did not include the requested type/mask when
getting a larval for the geniv algorithm that is to be constructed.

Signed-off-by: Herbert Xu