src/sys/opencrypto/cryptodev.c, branch releng/6.2

MFC: Synchronize opencrypto framework with HEAD version.

2006-09-04T15:16:14+00:00

MFC:

2006-03-01T21:40:14+00:00

  Connect zlib to the build.

  This patch fixes a problem, which exists if you have IPSEC in your kernel
  and want to have crypto support loaded as KLD. By moving zlib to separate
  module and adding MODULE_DEPEND directives, it is possible to use such
  configuration without complication. Otherwise, since IPSEC is linked with
  zlib (just like crypto.ko) you'll get following error:

          interface zlib.1 already present in the KLD 'kernel'!

  Approved by:    cognet (mentor)

Approved by:	re (scottl)

MFC: sys/opencrypto/cryptodev.c 1.26

2005-08-19T12:04:19+00:00

Fix bogus check. It was possible to panic the kernel by giving 0 length.
This is actually a local DoS, as every user can use /dev/crypto if there
is crypto hardware in the system and cryptodev.ko is loaded (or compiled
into the kernel).

Reported by:    Mike Tancsa 
Security:	Local DoS on systems with crypto HW and with /dev/crypto available
Approved by:	re (kensmith)

Use dynamic major number allocation.

2005-02-27T22:11:02+00:00

/* -> /*- for license, minor formatting changes

2005-01-07T02:29:27+00:00

Push Giant down through ioctl.

2004-11-17T09:09:55+00:00

Don't grab Giant in the upper syscall/wrapper code

NET_LOCK_GIANT in the socket code (sockets/fifos).

mtx_lock(&Giant) in the vnode code.

mtx_lock(&Giant) in the opencrypto code.  (This may actually not be
needed, but better safe than sorry).

Devfs grabs Giant if the driver is marked as needing Giant.

Don't acquire Giant in cryptof_close(), as the code is intended to be

2004-08-10T03:26:17+00:00

able to run MPsafe (and appears to be MPsafe).

Discussed with (some time ago):	sam

Push acquisition of Giant from fdrop_closed() into fo_close() so that

2004-07-22T18:35:43+00:00

individual file object implementations can optionally acquire Giant if
they require it:

- soo_close(): depends on debug.mpsafenet
- pipe_close(): Giant not acquired
- kqueue_close(): Giant required
- vn_close(): Giant required
- cryptof_close(): Giant required (conservative)

Notes:

  Giant is still acquired in close() even when closing MPSAFE objects
  due to kqueue requiring Giant in the calling closef() code.
  Microbenchmarks indicate that this removal of Giant cuts 3%-3% off
  of pipe create/destroy pairs from user space with SMP compiled into
  the kernel.

  The cryptodev and opencrypto code appears MPSAFE, but I'm unable to
  test it extensively and so have left Giant over fo_close().  It can
  probably be removed given some testing and review.

Do the dreaded s/dev_t/struct cdev */

2004-06-16T09:47:26+00:00

Bump __FreeBSD_version accordingly.

add missing #include

2004-05-30T20:27:19+00:00