rwatson 51a3d7f35d Don't allow VOP_GETEXTATTR to set uio->uio_offset != 0, as we don't ...

provide locking over extended attribute operations, requiring that
individual operations be atomic.  Allowing non-zero starting offsets
permits applications/etc to put themselves at risk for inconsistent
behavior.  As VOP_SETEXTATTR already prohibited non-zero write offsets,
this makes sense.

Suggested by:	Andreas Gruenbacher <a.gruenbacher@bestbits.at>

2000-05-03 05:50:46 +00:00

..

ffs

Remove unneeded #include <vm/vm_zone.h>

2000-04-30 18:52:11 +00:00

mfs

Convert the magic MFS device to a VCHR.

2000-04-22 05:45:38 +00:00

ufs

Don't allow VOP_GETEXTATTR to set uio->uio_offset != 0, as we don't

2000-05-03 05:50:46 +00:00