Messages in this thread | | | From | Ivan Babrou <> | Date | Wed, 3 Feb 2021 09:46:55 -0800 | Subject | Re: BUG: KASAN: stack-out-of-bounds in unwind_next_frame+0x1df5/0x2650 |
| |
> Can you pretty please not line-wrap console output? It's unreadable.
GMail doesn't make it easy, I'll send a link to a pastebin next time. Let me know if you'd like me to regenerate the decoded stack.
> > edfd9b7838ba5e47f19ad8466d0565aba5c59bf0 is the first bad commit > > commit edfd9b7838ba5e47f19ad8466d0565aba5c59bf0 > > Not sure what tree you're on, but that's not the upstream commit.
I mentioned that it's a rebased core-static_call-2020-10-12 tag and added a link to the upstream hash right below.
> > Author: Steven Rostedt (VMware) <rostedt@goodmis.org> > > Date: Tue Aug 18 15:57:52 2020 +0200 > > > > tracepoint: Optimize using static_call() > > > > There's a known issue with that patch, can you try: > > http://lkml.kernel.org/r/20210202220121.435051654@goodmis.org
I've tried it on top of core-static_call-2020-10-12 tag rebased on top of v5.9 (to make it reproducible), and the patch did not help. Do I need to apply the whole series or something else?
| |