From: Peter Zijlstra <peterz@infradead.org>
To: Ivan Babrou <ivan@cloudflare.com>
Cc: kernel-team <kernel-team@cloudflare.com>,
Ignat Korchagin <ignat@cloudflare.com>,
Hailong liu <liu.hailong6@zte.com.cn>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Miroslav Benes <mbenes@suse.cz>,
Julien Thierry <jthierry@redhat.com>,
Jiri Slaby <jirislaby@kernel.org>,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@redhat.com>,
dm-devel@redhat.com,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>, Andrii Nakryiko <andriin@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@chromium.org>, Robert Richter <rric@kernel.org>,
"Joel Fernandes (Google)" <joel@joelfernandes.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
bpf@vger.kernel.org
Subject: Re: BUG: KASAN: stack-out-of-bounds in unwind_next_frame+0x1df5/0x2650
Date: Wed, 3 Feb 2021 17:46:33 +0100 [thread overview]
Message-ID: <YBrTaVVfWu2R0Hgw@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CABWYdi27baYc3ShHcZExmmXVmxOQXo9sGO+iFhfZLq78k8iaAg@mail.gmail.com>
On Tue, Feb 02, 2021 at 07:09:44PM -0800, Ivan Babrou wrote:
> On Thu, Jan 28, 2021 at 7:35 PM Ivan Babrou <ivan@cloudflare.com> wrote:
> > ==================================================================
> > [ 128.368523][ C0] BUG: KASAN: stack-out-of-bounds in
> > unwind_next_frame (arch/x86/kernel/unwind_orc.c:371
> > arch/x86/kernel/unwind_orc.c:544)
> > [ 128.369744][ C0] Read of size 8 at addr ffff88802fceede0 by task
> > kworker/u2:2/591
Can you pretty please not line-wrap console output? It's unreadable.
> edfd9b7838ba5e47f19ad8466d0565aba5c59bf0 is the first bad commit
> commit edfd9b7838ba5e47f19ad8466d0565aba5c59bf0
Not sure what tree you're on, but that's not the upstream commit.
> 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
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Ivan Babrou <ivan@cloudflare.com>
Cc: Song Liu <songliubraving@fb.com>,
Mike Snitzer <snitzer@redhat.com>, Yonghong Song <yhs@fb.com>,
Ignat Korchagin <ignat@cloudflare.com>,
Alexei Starovoitov <ast@kernel.org>,
linux-mm@kvack.org, dm-devel@redhat.com,
Alexander Potapenko <glider@google.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Joel Fernandes \(Google\)" <joel@joelfernandes.org>,
Miroslav Benes <mbenes@suse.cz>,
Jiri Slaby <jirislaby@kernel.org>,
Alasdair Kergon <agk@redhat.com>,
Daniel Borkmann <daniel@iogearbox.net>,
kernel-team <kernel-team@cloudflare.com>,
Hailong liu <liu.hailong6@zte.com.cn>,
x86@kernel.org, John Fastabend <john.fastabend@gmail.com>,
kasan-dev@googlegroups.com, Ingo Molnar <mingo@redhat.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Andrii Nakryiko <andriin@fb.com>,
Robert Richter <rric@kernel.org>,
"Steven Rostedt \(VMware\)" <rostedt@goodmis.org>,
Borislav Petkov <bp@alien8.de>,
Josh Poimboeuf <jpoimboe@redhat.com>,
KP Singh <kpsingh@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>,
bpf@vger.kernel.org, Dmitry Vyukov <dvyukov@google.com>,
Julien Thierry <jthierry@redhat.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
Martin KaFai Lau <kafai@fb.com>
Subject: Re: [dm-devel] BUG: KASAN: stack-out-of-bounds in unwind_next_frame+0x1df5/0x2650
Date: Wed, 3 Feb 2021 17:46:33 +0100 [thread overview]
Message-ID: <YBrTaVVfWu2R0Hgw@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CABWYdi27baYc3ShHcZExmmXVmxOQXo9sGO+iFhfZLq78k8iaAg@mail.gmail.com>
On Tue, Feb 02, 2021 at 07:09:44PM -0800, Ivan Babrou wrote:
> On Thu, Jan 28, 2021 at 7:35 PM Ivan Babrou <ivan@cloudflare.com> wrote:
> > ==================================================================
> > [ 128.368523][ C0] BUG: KASAN: stack-out-of-bounds in
> > unwind_next_frame (arch/x86/kernel/unwind_orc.c:371
> > arch/x86/kernel/unwind_orc.c:544)
> > [ 128.369744][ C0] Read of size 8 at addr ffff88802fceede0 by task
> > kworker/u2:2/591
Can you pretty please not line-wrap console output? It's unreadable.
> edfd9b7838ba5e47f19ad8466d0565aba5c59bf0 is the first bad commit
> commit edfd9b7838ba5e47f19ad8466d0565aba5c59bf0
Not sure what tree you're on, but that's not the upstream commit.
> 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
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2021-02-03 16:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 3:35 [dm-devel] BUG: KASAN: stack-out-of-bounds in unwind_next_frame+0x1df5/0x2650 Ivan Babrou
2021-01-29 3:35 ` Ivan Babrou
2021-02-03 3:09 ` Ivan Babrou
2021-02-03 3:09 ` [dm-devel] " Ivan Babrou
2021-02-03 16:46 ` Peter Zijlstra [this message]
2021-02-03 16:46 ` Peter Zijlstra
2021-02-03 17:46 ` Ivan Babrou
2021-02-03 17:46 ` [dm-devel] " Ivan Babrou
2021-02-03 19:05 ` Josh Poimboeuf
2021-02-03 19:05 ` [dm-devel] " Josh Poimboeuf
2021-02-03 22:41 ` Ivan Babrou
2021-02-03 22:41 ` [dm-devel] " Ivan Babrou
2021-02-03 23:27 ` Josh Poimboeuf
2021-02-03 23:27 ` [dm-devel] " Josh Poimboeuf
2021-02-03 23:30 ` Ivan Babrou
2021-02-03 23:30 ` [dm-devel] " Ivan Babrou
2021-02-04 0:17 ` Josh Poimboeuf
2021-02-04 0:17 ` [dm-devel] " Josh Poimboeuf
2021-02-04 0:52 ` Ivan Babrou
2021-02-04 0:52 ` [dm-devel] " Ivan Babrou
2021-02-04 2:37 ` Josh Poimboeuf
2021-02-04 2:37 ` [dm-devel] " Josh Poimboeuf
2021-02-04 19:51 ` Ivan Babrou
2021-02-04 19:51 ` [dm-devel] " Ivan Babrou
2021-02-04 20:22 ` Josh Poimboeuf
2021-02-04 20:22 ` [dm-devel] " Josh Poimboeuf
2021-02-04 9:22 ` Peter Zijlstra
2021-02-04 9:22 ` [dm-devel] " Peter Zijlstra
2021-02-04 2:44 ` Steven Rostedt
2021-02-04 2:44 ` [dm-devel] " Steven Rostedt
2021-02-04 3:09 ` Josh Poimboeuf
2021-02-04 3:09 ` [dm-devel] " Josh Poimboeuf
2021-02-04 18:41 ` Ivan Babrou
2021-02-04 18:41 ` [dm-devel] " Ivan Babrou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YBrTaVVfWu2R0Hgw@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andriin@fb.com \
--cc=aryabinin@virtuozzo.com \
--cc=ast@kernel.org \
--cc=bp@alien8.de \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dm-devel@redhat.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=hpa@zytor.com \
--cc=ignat@cloudflare.com \
--cc=ivan@cloudflare.com \
--cc=jirislaby@kernel.org \
--cc=joel@joelfernandes.org \
--cc=john.fastabend@gmail.com \
--cc=jpoimboe@redhat.com \
--cc=jthierry@redhat.com \
--cc=kafai@fb.com \
--cc=kasan-dev@googlegroups.com \
--cc=kernel-team@cloudflare.com \
--cc=kpsingh@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liu.hailong6@zte.com.cn \
--cc=mathieu.desnoyers@efficios.com \
--cc=mbenes@suse.cz \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=rric@kernel.org \
--cc=snitzer@redhat.com \
--cc=songliubraving@fb.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yhs@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.