tick/rcu: Stop allowing RCU_SOFTIRQ in idle
Bug #1998857 reported by
Bodong Wang
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux-bluefield (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| Focal |
Fix Committed
|
Medium
|
Bodong Wang | ||
| Jammy |
Fix Committed
|
Medium
|
Bodong Wang | ||
Bug Description
* Explain the bug
RCU_SOFTIRQ used to be special in that it could be raised on purpose
within the idle path to prevent from stopping the tick. Some code still
prevents from unnecessary warnings related to this specific behaviour
while entering in dynticks-idle mode.
However the nohz layout has changed quite a bit in ten years, and the
removal of CONFIG_
safe-conduct. Now the RCU_SOFTIRQ vector is expected to be raised from
sane places.
* Brief explanation of fixes
Stop allowing RCU_SOFTIRQ in idle
* How to test
In boot dmesg, the warning should be gone.
* What it could break.
N/A
| Changed in linux-bluefield (Ubuntu Focal): | |
| assignee: | nobody → Bodong Wang (bodong-wang) |
| importance: | Undecided → Medium |
| status: | New → In Progress |
| Changed in linux-bluefield (Ubuntu Jammy): | |
| assignee: | nobody → Bodong Wang (bodong-wang) |
| importance: | Undecided → Medium |
| status: | New → In Progress |
| Changed in linux-bluefield (Ubuntu Focal): | |
| status: | In Progress → Fix Committed |
| Changed in linux-bluefield (Ubuntu Jammy): | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote | #1 |
| tags: | added: kernel-spammed-jammy-linux-bluefield verification-needed-jammy |
| tags: |
added: verification-done-jammy removed: kernel-spammed-jammy-linux-bluefield verification-needed-jammy |
To post a comment you must log in.
This bug is awaiting verification that the linux-bluefield
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/