Re: [BUG REPORT] Soft Lockup in smp_call_function_single+0xD8

From: Jeff Merkey
Date: Sat Jan 30 2016 - 13:51:24 EST

> Just so you know, I have no intention of supporting this use case. In
> fact, I'm planning to eventually stop using IST for #DB entirely, at
> which point the kernel will crash terribly if this code is
> single-stepped (except when using a hypervisor to do this single
> stepping, which is a much more sensible way to handle it).

I don't know what good using the userspace trap code is going to
help with this, a hypervisor will crash too with sysret being used
there -- I just tested it.

So it breaks all debuggers, even the faux ones that run as user space
apps. Your
other suggestions will cause some mayhem too for debuggers. If you
break something, I'll just unpatch it in my tree, so have fun. LOL