dohqu8Zi

Thanks for the correction.

BTW: Depending on the configuration you can create a new namespace within Docker to gain CAP_NET_RAW since namespaces can nest.

No, Docker usually drops CAP_NET_RAW within the container. But you can change that and other container technologies definitely keep CAP_NET_RAW within the container.

No.

Create a new user namespace and you have CAP_NET_RAW within your shiny new namespace.

The bug is already fixed and they have better things to do than messing with our trolling. :-)

I hope to see a mainline submission for public review of this soon.

The majority of OpenWRT/LEDE patches are gross hacks that need a major rework or a completely different approach. This is not the first patch of that kind.

Sadly, the author failed to read on the history of kdbus and AF_BUS.

Just using UNIX domain socks is not the solution. This is more or less what dbus currently does and has major issues with memory accounting and trusts.

Original announcement with hipster mode off. ;) http://marc.info/?l=git&m=147286906121492&w=2

So, this is http://shimmer.sourceforge.net/ rewritten in go?

Only in corner cases you want to replace all syscalls to LKL calls. Often you need to call to the host as well. Especially LKL itself needs...

Depends on the FUSE filesystem, but most of the time it is the kernel<->user copy process.

This does not make any sense. As soon you issue any system call you will trigger a context switch. So, eve without using FUSE and just using LKL as tool to extract your favorite filesystem it will face them.

But the context switches not the bottleneck in FUSE. Did you benchmark?