[sexenteen]

拉取/合并请求描述：(PR description)

[

为什么提交这份PR (why to submit this PR)

core.signal has no case covering "a signal sent to a thread that is blocked in a timer
delay". That is the path behind PR #7663 ("被动挂起的线程，无法处理信号") and the behaviour
described in the discussion there:

thread1 调用 rt_thread_delay，然后 thread2 给 thread1 发信号：会唤醒 thread1，但是 thread1
并不会执行信号函数

On current master this scenario does work (verified manually: the woken thread continued after
~10 ticks instead of 100, and its handler ran), but nothing in the utest suite keeps it
working. This adds a regression case so that a future change in _signal_deliver() or in the
scheduler cannot silently break it again.

你的解决方案是什么 (what is your solution)

A new utest case rt_signal_delay_thread_test() (case 10) in src/utest/signal_tc.c:

• sig_t2 installs SIGUSR1, unmasks it, then blocks in rt_thread_mdelay(1000) (1 s);
• the testcase thread sends SIGUSR1 to it and waits on a semaphore for at most 500 ms;
• assertions: rt_thread_kill() returns RT_EOK, the semaphore is released within 500 ms (so the
  thread was woken before its 1 s delay expired), and receive_sig == SIGUSR1 (so the handler
  really ran in that thread).

Only src/utest/signal_tc.c is touched (+35/-0). No kernel code is changed, and the existing
cases 1-9 are left as they are.

请提供验证的bsp和config (provide the config and bsp)

• BSP: bsp/qemu-vexpress-a9
• .config: CONFIG_RT_USING_UTESTCASES=y, CONFIG_RT_UTEST_SIGNAL=y (enabled temporarily to run
  this case; the BSP configuration itself is not part of this PR)
• action: https://github.com/sexenteen/rt-thread/actions/runs/41409141304

Verification:

msh />utest_run core.signal
[==========] utest unit name: (rt_signal_install_test)
...
[==========] utest unit name: (rt_signal_delay_thread_test)
[  PASSED  ] [ result   ] testcase (core.signal)
[  PASSED  ] [ result   ] 1 tests.

scons -j4 passes and tools/ci/clang_format_check.py reports "clang-format check success"
for the changed file.

Not covered: RT_USING_SMART (LWP) and RT_USING_SMP, which take different branches inside
_signal_deliver(); only the single-core non-SMART path is exercised.
]

当前拉取/合并请求的状态 Intent for your PR

必须选择一项 Choose one (Mandatory):

• 本拉取/合并请求是一个草稿版本 This PR is for a code-review and is intended to get feedback
• 本拉取/合并请求是一个成熟版本 This PR is mature, and ready to be integrated into the repo

代码质量 Code Quality：

我在这个拉取/合并请求中已经考虑了 As part of this pull request, I've considered the following:

• 已经仔细查看过代码改动的对比 Already check the difference between PR and old code
• 代码风格正确，包括缩进空格，命名及其他风格 Style guide is adhered to, including spacing, naming and other styles
• 没有垃圾代码，代码尽量精简，不包含#if 0代码，不包含已经被注释了的代码 All redundant code is removed and cleaned up
• 所有变更均有原因及合理的，并且不会影响到其他软件组件代码或BSP All modifications are justified and not affect other components or BSP
• 对难懂代码均提供对应的注释 I've commented appropriately where code is tricky
• 代码是高质量的 Code in this PR is of high quality
• 已经使用clang-format 源码格式化工具确保格式符合RT-Thread代码规范 This PR has been formatted with clang-format and complies with RT-Thread code specification
• 如果是新增bsp, 已经添加ci检查到.github/ALL_BSP_COMPILE.json 详细请参考链接BSP自查

[github-actions]

👋 感谢您对 RT-Thread 的贡献！Thank you for your contribution to RT-Thread!

为确保代码符合 RT-Thread 的编码规范，请在你的仓库中执行以下步骤运行代码格式化工作流（如果格式化CI运行失败）。
To ensure your code complies with RT-Thread's coding style, please run the code formatting workflow by following the steps below (If the formatting of CI fails to run).

---

🛠 操作步骤 | Steps

1. 前往 Actions 页面 | Go to the Actions page
   点击进入工作流 → | Click to open workflow →

2. 点击 Run workflow | Click Run workflow

• Use workflow from 保持默认分支（通常为 master）
  Keep the default branch (usually master) in Use workflow from
• 在 branch 输入框填写 PR 分支 test/issue-7654-signal-blocked-thread
  Enter PR branch test/issue-7654-signal-blocked-thread in the branch field
• 设置需排除的文件/目录（目录请以"/"结尾）
  Set files/directories to exclude (directories should end with "/")

3. 等待工作流完成 | Wait for the workflow to complete
   格式化后的代码将作为独立提交推送至你的分支。
   The formatting changes will be pushed to your branch as a separate commit.

完成后，提交将自动更新至 test/issue-7654-signal-blocked-thread 分支，关联的 Pull Request 也会同步更新。
Once completed, commits will be pushed to the test/issue-7654-signal-blocked-thread branch automatically, and the related Pull Request will be updated.

如有问题欢迎联系我们，再次感谢您的贡献！💐
If you have any questions, feel free to reach out. Thanks again for your contribution!

[github-actions]

📌 Code Review Assignment

🏷️ Tag: kernel

Reviewers: @GorrayLi @ReviewSun @hamburger-os @lianux-mm @wdfk-prog @xu18838022837

Changed Files (Click to expand)

• src/utest/signal_tc.c

---

📊 Current Review Status (Last Updated: 2026-11-02 15:53 CST)

• ⌛ @GorrayLi Pending Review
• ⌛ @ReviewSun Pending Review
• ⌛ @hamburger-os Pending Review
• ⌛ @lianux-mm Pending Review
• ⌛ @wdfk-prog Pending Review
• ⌛ @xu18838022837 Pending Review

---

📝 Review Instructions

1. 维护者可以通过单击此处来刷新审查状态: 🔄 刷新状态
   Maintainers can refresh the review status by clicking here: 🔄 Refresh Status

2. 确认审核通过后评论 LGTM/lgtm
   Comment LGTM/lgtm after confirming approval

3. PR合并前需至少一位维护者确认
   PR must be confirmed by at least one maintainer before merging

ℹ️ 刷新CI状态操作需要具备仓库写入权限。
ℹ️ Refresh CI status operation requires repository Write permission.