Changqing Li 7bb2862899 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] 686da19abb [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>		2024-04-11 23:32:35 -07:00
..
nodejs	nodejs: don't always disable io_uring	2024-04-11 23:32:35 -07:00
nodejs-oe-cache-20.11	nodejs: update to latest v20 version 20.11.0	2024-02-14 08:24:48 -08:00
nodejs_20.11.1.bb	nodejs: don't always disable io_uring	2024-04-11 23:32:35 -07:00
nodejs-oe-cache-native_20.11.bb	nodejs: update to latest v20 version 20.11.0	2024-02-14 08:24:48 -08:00