clone 768905 -1
retitle -1 keyutils: Work around FTBFS on non-release kernels
severity -1 important
thanks
On 2014-11-23 15:44, Adam Borowski wrote:
> On Sun, Nov 23, 2014 at 12:55:22PM +0100, Christian Kastner wrote:
>>> The syscall is returning ENOKEY where until 3.16 it was returning EPERM.
>>
>> I am now quite certain that the issue is being caused by this kernel
>> commit in 3.17:
>>
>> Commit: a4e3b8d79a5c6d40f4a9703abf7fe3abcc6c3b8d
>> KEYS: special dot prefixed keyring name bug fix
>
> Except, it fails with earlier kernels too: I tested 3.8 on armhf and 3.11 on
> amd64 (the latter with config identical to Debian's in all "uninteresting"
> to me areas).
I tested this with kernels 3.8 - 3.14 and can verify this issue existed
up to 3.12.
It's a separate (although similar) issue as above: a wrong errno is
returned. It was fixed by the following commit (which entered kernel 3.13):
Commit: 61ea0c0ba904a55f55317d850c1072ff7835ac92
KEYS: Skip key state checks when checking for possession
Since this issue affects only non-release Debian kernels, I'll just be
adding a patch that works around this issue in the affected kernels, and
add a README documenting this issue.
Regards,
Christian
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
