hm. Bigger vmlinux, smaller .text.
It means that we'll hit handle_BUG with that extra EIP pushed on the stack.Dunno. I was hoping Andi would pop up with the appropriate CFI gunk, if necessary. But the reason for making it a call was to make it as unwindable as possible.
What does that do to the stack trace, and to the unwinder?
It'll also muck up the displayed EIP, not that that matters a lot (well, it
might matter a bit if the BUG is in an inlined function).
We could get the correct EIP by fishing it off the stack (and subtracting
five from it?)
Or we could assume that BUG doesn't return (it doesn't) and make that call
a jmp. But then we'd really lose the EIP.