Once again lddpd fails to start with seccomp enabled Reproducible: Always Steps to Reproduce: 1. build lldpd with +seccomp 2. start 3. crash/exit Actual Results: lldpd fails to start up and bails out, again a seccomp issue (as with 0.9.1 #577576) this time it is about mprotect() being called (which seems to be disallowed). Expected Results: A working lldpd Maybe the ebuild should default to -seccomp in ISUE until the authors get seccomp into a mature state within lldpd?
The ebuild does default to -seccomp, you must have it enabled globally in your make.conf. This should be fixed via a patch in net-misc/lldpd-0.9.5, I have also opened a PR upstream: https://github.com/vincentbernat/lldpd/pull/213
Nope, no seccomp in make.conf. Last time I checked, the ebuild had seccomp instead of -seccomp in IUSE, so it does not forcefully disable seccomp, even though lldpd is repeatedly broken with regards to seccomp. (Not enabling it is a different state). seccomp might be enabled by a profile.
BTW: v0.9.5 bails for sendmmsg. Looks like the lddpd folks are getting nowhere with their seccomp stuff.
Created attachment 455044 [details, diff] lldpd-0.9.5-seccomp-add-sendmmsg.patch This patch should help with that, please test it and report if you have any other issues. Feel free to add an entry to package.use to disable the seccomp USE flag if you want.
Invalid syscall attempted: recvfrom(45) Invalid syscall not allowed: stop here
After adding recvfrom lldpd seems to start.
