** Also affects: linux-bluefield (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-bluefield (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-bluefield (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux-bluefield (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-bluefield (Ubuntu Focal)
Assignee: (unassigned) => Bodong Wang (bodong-wang)
** Changed in: linux-bluefield (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-bluefield (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-bluefield (Ubuntu Jammy)
Assignee: (unassigned) => Bodong Wang (bodong-wang)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/1998857
Title:
tick/rcu: Stop allowing RCU_SOFTIRQ in idle
Status in linux-bluefield package in Ubuntu:
New
Status in linux-bluefield source package in Focal:
In Progress
Status in linux-bluefield source package in Jammy:
In Progress
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_RCU_FAST_NO_HZ has been the final straw to this
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1998857/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
