NET_NS=n leads to strange program header in liblinux.so about net-next-nuse HOT 4 OPEN

Actually, I was wrong --- CONFIG_NET_NS=y leads to a build error. The other solution still works, though.

from net-next-nuse.

thanks for the issue report (and sorry to be late).

it's indeed a problem with the inappropriate elf header and would be great if we can work with valgrind, which is always useful.

this is a bit off-topic though but I've been thinking to this arch/lib code to migrate into LKL (linux kernel library), which I'm recently working on. i'm not yet porting all the stuff of net-next-nuse but i see the bright future with a clean design of lkl, which I expect to solve several issues of this repo (including #45).

https://github.com/libos-nuse/lkl-linux is my working repository. it would be great if you still see this issue in lkl-linux.

from net-next-nuse.

@thehajime I'll take a look at it. This was an extraordinarily weird problem --- I'd be surprised if it turned up again.

Which branch of that repo is the most current one?

from net-next-nuse.

(sorry for the cross-post)

I would suggest to use https://github.com/lkl/linux, not my branch (https://github.com/libos-nuse/lkl-linux) as mine is unstable while the upstream is relatively stable.

from net-next-nuse.