| Summary: | app-misc/pax-utils-1.1[seccomp]: scanelf: seccomp_load failed: Invalid argument when kernel lacks CONFIG_SECCOMP | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Piotr Karbowski (RETIRED) <slashbeast> |
| Component: | [OLD] Core system | Assignee: | SpanKY <vapier> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | dark.shadow, floppym |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
duping to a newer bug because it has more details *** This bug has been marked as a duplicate of bug 558482 *** not a dupe ... read it too fast *** Bug 558954 has been marked as a duplicate of this bug. *** note: this is a non-fatal warning and shouldn't cause any problems when emerging i've changed the seccomp code to ignore EINVAL since that's what the kernel returns when seccomp is disabled. kind of sucks, but so it goes. http://gitweb.gentoo.org/proj/pax-utils.git/commit/?id=6fa4f469c4b0f44259b1cc8c984bfcaa655a2f83 |
I've noticed that I am getting a lot of errors like scanelf: seccomp_load failed: Invalid argument While running emerge. scanelf from pax-utils does have seccomp useflag enabled but my kernel does not have CONFIG_SECCOMP symbol. Until recently it wasn't like that. Reproducible: Always