On Thu, Jul 13, 2017 at 07:21:15AM -0500, Josh Poimboeuf wrote: > On Thu, Jul 13, 2017 at 07:17:55AM -0500, Josh Poimboeuf wrote: > > BTW, while we're throwing out ideas for this, here's another idea, > > though it's almost certainly not a good one :-) > > > > For user space stack unwinding, the kernel could emulate what the kernel > > 'guess' unwinder does by scanning the user space stack and returning all > > the text addresses it finds. To clarify, text address would mean any address in a VMA with the executable bit set. > > The results wouldn't be 100% accurate, but they could end up being > > useful over time. > > And to expound further on the bad idea, maybe the "bad" addresses could > be filtered out somehow in post-processing (insert lots of hand waving). And some details on the post-processing: in most cases it should be possible to determine which of the found stack addresses are valid by looking at the call instructions immediately preceding the stack text addresses, and making sure the call target points to the same function as the previously found address. But of course that wouldn't work for indirect calls. -- Josh -- To unsubscribe from this list: send the line "unsubscribe live-patching" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
