[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: chroot/aarch64 issues
From: |
Ludovic Courtès |
Subject: |
Re: chroot/aarch64 issues |
Date: |
Tue, 05 Jul 2016 16:44:15 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Efraim Flashner <address@hidden> skribis:
> On Tue, Jul 05, 2016 at 10:45:51AM +0200, Ludovic Courtès wrote:
>> Efraim Flashner <address@hidden> skribis:
>>
>> > On Mon, Jul 04, 2016 at 03:37:12PM +0200, Ludovic Courtès wrote:
>> >> Hi!
>>
>> If the kernel config corresponds to this kernel, I don’t see which of
>> the other EINVAL reasons given in clone(2) would apply. Does ‘dmesg’
>> show something?
>>
>> Could you maybe try a C program that invokes clone(2) and progressively
>> remove CLONE_ flags until you find the one that’s causing EINVAL?
>>
>> Thanks,
>> Ludo’.
>
> I grabbed the code from man 2 clone and ran that on the odroid, which
> told me "clone: Operation not permitted"
This is expected; quoth clone(2):
--8<---------------cut here---------------start------------->8---
EPERM CLONE_NEWIPC, CLONE_NEWNET, CLONE_NEWNS, CLONE_NEWPID, or CLONE_NEWUTS
was specified by an unprivi‐
leged process (process without CAP_SYS_ADMIN).
--8<---------------cut here---------------end--------------->8---
Can you try running it as root?
Ludo’.