diff options
| author | Hongxu Jia <hongxu.jia@windriver.com> | 2021-08-29 06:52:35 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2021-08-31 20:51:11 +0100 |
| commit | 40305d389e8a8d19f4b98cf4d36213fdf281e5b3 (patch) | |
| tree | 77f071ec309eb8b758e2148258e1ccbb1a6a5c70 /meta/classes/kernel.bbclass | |
| parent | a5b257006b2c480d86e09909cdafb3c8ba05b863 (diff) | |
| download | poky-40305d389e8a8d19f4b98cf4d36213fdf281e5b3.tar.gz | |
glibc: fix create thread failed in unprivileged process
Since upstream commit [d8ea0d0168 Add an internal wrapper for clone, clone2
and clone3] applied, start a unprivileged container (docker run without
--privileged), it creates a thread failed in container.
In commit d8ea0d0168, it calls __clone3 if HAVE_CLONE3_WAPPER is defined. If
__clone3 returns -1 with ENOSYS, fall back to clone or clone2.
As known from [1], cloneXXX fails with EPERM if CLONE_NEWCGROUP,
CLONE_NEWIPC, CLONE_NEWNET, CLONE_NEWNS, CLONE_NEWPID, or CLONE_NEWUTS
was specified by an unprivileged process (process without CAP_SYS_ADMIN)
[1] https://man7.org/linux/man-pages/man2/clone3.2.html
So if __clone3 returns -1 with EPERM, fall back to clone or clone2 could
fix the issue.
(From OE-Core rev: 234a3e84640c1bb6df5fa4d3d7089a854b19d108)
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/kernel.bbclass')
0 files changed, 0 insertions, 0 deletions