* KaiGai Kohei (kaigai@ak.jp.nec.com) wrote:
quoted text
> Chris, what is the status of the patch?

I still don't understand how ...

quoted text
>> When we run a userspace utility on the latest kernel, it has to be compiled
>> with kernel-headers which have same capability set at least.
>> If installed userspace utility does not support newly added capabilities,
>> it requires users to rebuild their utilities when they update the kernel.
>>
>> Typically, kernel developer faces this kind of version mismatching.
>> When they boots their kernel with new capabilities, it also requires to
>> rebuild libcap. Then, they have to revert it, when they boots with normal
>> kernel.
>>
>> If libcap can know what capabilities are supported on the running kernel
>> automatically, it does not need users to rebuild libcap concurrently.

...libcap can do anything meaningful here with capabilities it doesn't
know about?  This interface is already versioned, what is wrong is old
cap version on new kernel (clearly new cap version on old kernel would
have to fall back to older cap version)?

thanks,
-chris
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/