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
..
2000-05-01 20:32:07 +00:00
2000-05-01 20:32:07 +00:00
2000-05-01 20:32:07 +00:00
2000-05-01 20:32:07 +00:00
2000-05-01 20:32:07 +00:00
2000-05-01 20:32:07 +00:00
2000-05-01 20:32:07 +00:00
2000-05-01 20:32:07 +00:00
2000-03-29 17:12:09 +00:00
2000-05-01 20:32:07 +00:00
2000-01-15 05:15:06 +00:00
2000-05-01 20:32:07 +00:00
2000-04-29 13:34:28 +00:00
2000-05-01 20:32:07 +00:00
2000-05-01 20:32:07 +00:00
2000-05-01 20:32:07 +00:00
1999-08-27 23:45:13 +00:00