RFC Tracing, Idle, RCU and such goodness
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest3 patches 8 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | sched,idle,rcu: Push rcu_idle deeper into the idle pathdrivers/ kernel/ | +15 | 0 replies | |
| 2/3 | locking,entry: #PF vs TRACE_IRQFLAGSinclude/ kernel/ | +26 | 4 replies | |
| 3/3 | lockdep,trace: Expose tracepointskernel/ | +18 | 1 reply | |
| 3/3 | lockdep,trace: Expose tracepointskernel/ | +9 | 0 replies |
Reviews trailers per patch
2 of 4 patches have a Reviewed-by or Acked-by.
| Patch | Steven Rosted (VMware) | Paul E. McKenney |
|---|---|---|
| Series | T-b | |
| 1/3 | ||
| 2/3 | ||
| 3/3 | R-b | |
| 3/3 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [RFC][PATCH 0/3] Tracing, Idle, RCU and such goodness
Hi,
Syzbot report:
https://lkml.kernel.org/r/[email protected]
triggered a whole bunch of fallout.
These 3 patches are in reverse order of discovery. With them applied the reproducer no longer triggers and the machine boots without errors.
I also spend half the day trying to rewrite TRACE_IRQFLAGS, but so far haven't had success. I have the feeling that there's something slightly simpler hiding in there, but so far it doesn't want to come out.
Please, look carefully, this is all tricky code, and it's been a long and hot day here, mistakes are almost guaranteed :/
I also want to remove the _rcuidle() from trace_preemptirq.c, but given this was quite enough, I didn't touch those.