[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 10:45:51 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Efraim Flashner <address@hidden> skribis:
> On Mon, Jul 04, 2016 at 03:37:12PM +0200, Ludovic Courtès wrote:
>> Hi!
>>
>> Efraim Flashner <address@hidden> skribis:
>>
>> > On the side I'm working on the aarch64 port, and I've come across a
>>
>> Woohoo!
>>
>> > snag. I've been unable to actually get anything to build. When I start
>> > the daemon as:
>> > `sudo ./pre-inst-env guix-daemon --build-users-group=guixbuild',
>> > when I attempt to build hello I get back the error:
>> > guix build: error: build failed: cloning builder process: Invalid argument
>>
>> Could you strace the daemon itself?
>>
>> sudo ./pre-inst-env strace -f -o log guix-daemon \
>> --build-users-group=guixbuild
>>
>> I presume EINVAL is returned by clone(2), but it would be good to see
>> that syscall precisely.
>
> attached
The culprit is:
4871 clone(child_stack=0x7fd850d338,
flags=CLONE_NEWNS|CLONE_NEWUTS|CLONE_NEWIPC|CLONE_NEWPID|CLONE_NEWNET|SIGCHLD)
= -1 EINVAL (Invalid argument)
>> What Linux version is this?
>
> $ uname -a
> Linux odroid-jessie64 3.14.65+ #2 SMP PREEMPT Sun Jul 3 18:29:45
> UTC 2016 aarch64 GNU/Linux
According to clone(2), this version supports all of the above flags.
Also, the kernel config you posted has all the namespace options
enabled:
--8<---------------cut here---------------start------------->8---
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
--8<---------------cut here---------------end--------------->8---
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’.