> Quoting Chris Wright (
chrisw@sous-sol.org):
>> * Serge E. Hallyn (
serge@hallyn.com) wrote:
>>> I guess now that I've written this out, it seems pretty clear
>>> that capget64() and capget64() are the way to go. Any objections?
>> How is capget64() different from capget() that supports 2 different
>> header->versions (I thought that was the whole point of the versioned,
>> rather opaque interface)? I don't object to a new syscall, but I don't
>> see why it's required to avoid breaking libcap.
>
> Hmm, I guess it *works*, it's just harder to explain the "inconsistent"
> behavior. Now instead of saying "capget() will fail under certain
> conditions while capget64() will always succeed", capget() will actually
> fail under certain conditions only if you send in a certain header.
>
> Again, once I've written it out, I guess it isn't *so* bad.
