diff options
author | Changqing Li <changqing.li@windriver.com> | 2024-04-11 16:24:16 +0800 |
---|---|---|
committer | Khem Raj <raj.khem@gmail.com> | 2024-04-11 23:32:35 -0700 |
commit | 7bb28628991ec9be9610540401f7c6cc4c19997f (patch) | |
tree | e41b8a47f74277ca48da65bd6158cc88305bc65e /meta-python/recipes-devtools/python/python3-sqlparse/run-ptest | |
parent | 0bc241c5ab63795dc64d7d9c7907ad4056b0f2af (diff) | |
download | meta-openembedded-7bb28628991ec9be9610540401f7c6cc4c19997f.tar.gz |
nodejs: don't always disable io_uring
The original idea was always disable io_uring to avoid follwing failure
even when UV_USE_IO_URING is set to true, refer [1][2]:
0608: try:
*** 0609: update_hash(" %10s" % pwd.getpwuid(s.st_uid).pw_name)
0610: update_hash(" %10s" % grp.getgrgid(s.st_gid).gr_name)
0611: except KeyError as e:
0612: msg = ("KeyError: %s\nPath %s is owned by uid %d, gid %d, which doesn't match "
0613: "any user/group on target. This may be due to host contamination." %
Exception: Exception: KeyError: 'getpwuid(): uid not found: 20561'
But since 20.11.1, for fix CVE-2024-22017, io_uring is disabled by
default, refer [3]. So maybe patch
0001-deps-disable-io_uring-support-in-libuv.patch is not needed.
For case UV_USE_IO_URING is set to true, user can fix above failure
by "chown root:root -R ${D}" in do_install.
[1] https://lists.openembedded.org/g/openembedded-devel/message/105583
[2] https://bugzilla.yoctoproject.org/show_bug.cgi?id=15244
[3] https://github.com/nodejs/node/commit/686da19abbb83b7e01d48be19f832ab081b87084
[4] https://nvd.nist.gov/vuln/detail/CVE-2024-22017
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Diffstat (limited to 'meta-python/recipes-devtools/python/python3-sqlparse/run-ptest')
0 files changed, 0 insertions, 0 deletions