rt-thread.git/components, branch copilot/fix-sys-getaddrinfo-bug

chore: align getaddrinfo hints copy flow

2026-06-09T06:57:25Z

chore: simplify getaddrinfo user copy checks

2026-06-09T06:56:37Z

chore: tighten getaddrinfo user checks

2026-06-09T06:55:42Z

chore: clarify getaddrinfo user pointer handling

2026-06-09T06:54:39Z

chore: refine getaddrinfo validation locals

2026-06-09T06:53:21Z

fix: validate nested getaddrinfo user pointers

2026-06-09T06:51:59Z

[feat][soft_i2c]:change soft i2c default bus name

2026-06-08T07:13:11Z

[bsp][zynqmp-a53-dfzu2eg] enable full dm

2026-06-08T06:57:37Z

This is a builtin fdt example BSP Signed-off-by: GuEe-GUI <2991707448@qq.com>

[components][drivers][usb] add the missing file and fix build error for cherryusb

2026-06-02T09:41:34Z

lwp: fix pid leak on exec failure before task startup

2026-05-26T08:56:36Z

When msh tries to execute a non-ELF path, lwp_execve() may allocate a PID before lwp_load() fails. The old error path only dropped the LWP reference, leaving the PID tree entry pointing to a freed LWP. In an init-less boot flow, this can poison pid 1 after a failed command from msh. A later LWP launch may then treat the stale pid 1 entry as a valid parent LWP, resulting in invalid pgrp/session state and a job-control assertion during process exit. Add lwp_pid_rollback() for exec/spawn failures before the process becomes runnable. Unlike lwp_pid_put(), it always releases the PID lock and does not enter the "no more pid allocation" state when the PID tree becomes empty. Use the rollback helper in lwp_execve() failure paths after PID allocation. Signed-off-by: zhangyang