remove printk() from J_ASSERT macros
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | jbd: remove printk() from J_ASSERT macrosinclude/ | +1 | 0 replies | |
| 2/2 | jbd2: remove printk() from J_ASSERT macrosinclude/ | +1 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] remove printk() from J_ASSERT macros
The printk() in J_ASSERT clobbers registers, making it more difficult to determine what caused the assertion failure. We can deduce the assertion itself from the line number in the BUG() message, so let's just use that, and keep our registers intact for better debugging. While the hood is up, also remove a superfluous #define/#ifdef.
-- Chris