Robert Watson aad65d6f79 o Correct an ACL implementation bug that could result in a system panic ... under heavy use when default ACLs were bgin inherited by new files or directories. This is done by removing a bug in default ACL reading, and improving error handling for this failure case: - Move the setting of the buffer length (len) variable to above the ACL type (ap->a_type) switch rather than having it only for ACL_TYPE_ACCESS. Otherwise, the len variable is unitialized in the ACL_TYPE_DEFAULT case, which generally worked right, but could result in failure. - Add a check for a short/long read of the ACL_TYPE_DEFAULT type from the underlying EA, resulting in EPERM rather than passing a potentially corrupted ACL back to the caller (resulting "cleaner" failures if the EA is damaged: right now, the caller will almost always panic in the presence of a corrupted EA). This code is similar to code in the ACL_TYPE_ACCESS handling in the previous switch case. - While I'm fixing this code, remove a redundant bzero() of the ACL reader buffer; it need only be initialized above the acl_type switch. Obtained from: TrustedBSD Project		2001-04-02 01:02:32 +00:00
..
ffs	Fix typo ); -> ,	2001-03-24 15:25:04 +00:00
ifs	Change and clean the mutex lock interface.	2001-02-09 06:11:45 +00:00
mfs	Send the remains (such as I have located) of "block major numbers" to	2001-03-26 12:41:29 +00:00
ufs	o Correct an ACL implementation bug that could result in a system panic	2001-04-02 01:02:32 +00:00