src/sys/opencrypto/cryptodev.c, branch release/6.0.0_cvs

This commit was manufactured by cvs2svn to create tag

2005-11-03T00:35:26Z

'RELENG_6_0_0_RELEASE'. This commit was manufactured to restore the state of the 6.0-RELEASE image.

MFC: sys/opencrypto/cryptodev.c 1.26

2005-08-19T12:04:19Z

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:02Z

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

2005-01-07T02:29:27Z

Push Giant down through ioctl.

2004-11-17T09:09:55Z

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:17Z

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:43Z

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:26Z

Bump __FreeBSD_version accordingly.

add missing #include

2004-05-30T20:27:19Z

Device megapatch 4/6:

2004-02-21T21:10:55Z

Introduce d_version field in struct cdevsw, this must always be initialized to D_VERSION. Flip sense of D_NOGIANT flag to D_NEEDGIANT, this involves removing four D_NOGIANT flags and adding 145 D_NEEDGIANT flags.