On Thu, Feb 04, 2021 at 11:51:44AM -0800, Ivan Babrou wrote:
> > .macro FUNC_SAVE
> > #the number of pushes must equal STACK_OFFSET
> > + push%rbp
> > + mov %rsp, %rbp
> > push%r12
> > push%r13
> > push%r14
> > @@ -271,12 +273,14
On Wed, Feb 3, 2021 at 4:17 PM Josh Poimboeuf wrote:
>
> On Wed, Feb 03, 2021 at 03:30:35PM -0800, Ivan Babrou wrote:
> > > > > Can you recreate with this patch, and add "unwind_debug" to the
> > > > > cmdline?
> > > > > It will spit out a bunch of stack data.
> > > >
> > > > Here's the three I'm
On Wed, Feb 3, 2021 at 7:10 PM Josh Poimboeuf wrote:
> This line gives a big clue:
>
> [160676.608966][C4] RIP: 0010:0xc17d814c
>
> That address, without a function name, most likely means that it was
> running in some generated code (mostly likely BPF) when it got
> interrupted.
W
On Wed, Feb 03, 2021 at 09:46:55AM -0800, Ivan Babrou wrote:
> > 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.
Not my problem that you c
On Wed, Feb 03, 2021 at 09:44:48PM -0500, Steven Rostedt wrote:
> > > [ 128.441287][C0] RIP: 0010:skcipher_walk_next
> > > (crypto/skcipher.c:322 crypto/skcipher.c:384)
>
> Why do we have an RIP in skcipher_walk_next, if its the unwinder that
> had a bug? Or are they related?
>
> Or did skci
h:
> >
> > [ 128.367231][C0]
> > ==============
> > [ 128.368523][C0] BUG: KASAN: stack-out-of-bounds in
> > unwind_next_frame (arch/x86/kernel/unwind_orc.c:371
The bug is a stack-out-of-bounds error in unwind_orc.c, right?
> > arch/x86/kernel/unwind_orc.c:544)
> &
On Wed, Feb 03, 2021 at 04:52:42PM -0800, Ivan Babrou wrote:
> We also have the following stack that doesn't touch any crypto:
>
> * https://gist.github.com/bobrik/40e2559add2f0b26ae39da30dc451f1e
Can you also run this through decode_stacktrace.sh?
Both are useful (until I submit a fix for decod
On Wed, Feb 3, 2021 at 4:17 PM Josh Poimboeuf wrote:
>
> On Wed, Feb 03, 2021 at 03:30:35PM -0800, Ivan Babrou wrote:
> > > > > Can you recreate with this patch, and add "unwind_debug" to the
> > > > > cmdline?
> > > > > It will spit out a bunch of stack data.
> > > >
> > > > Here's the three I'm
On Wed, Feb 03, 2021 at 03:30:35PM -0800, Ivan Babrou wrote:
> > > > Can you recreate with this patch, and add "unwind_debug" to the cmdline?
> > > > It will spit out a bunch of stack data.
> > >
> > > Here's the three I'm building:
> > >
> > > * https://github.com/bobrik/linux/tree/ivan/static-cal
On Wed, Feb 3, 2021 at 3:28 PM Josh Poimboeuf wrote:
>
> On Wed, Feb 03, 2021 at 02:41:53PM -0800, Ivan Babrou wrote:
> > On Wed, Feb 3, 2021 at 11:05 AM Josh Poimboeuf wrote:
> > >
> > > On Wed, Feb 03, 2021 at 09:46:55AM -0800, Ivan Babrou wrote:
> > > > > Can you pretty please not line-wrap co
On Wed, Feb 03, 2021 at 02:41:53PM -0800, Ivan Babrou wrote:
> On Wed, Feb 3, 2021 at 11:05 AM Josh Poimboeuf wrote:
> >
> > On Wed, Feb 03, 2021 at 09:46:55AM -0800, Ivan Babrou wrote:
> > > > Can you pretty please not line-wrap console output? It's unreadable.
> > >
> > > GMail doesn't make it e
On Wed, Feb 3, 2021 at 11:05 AM Josh Poimboeuf wrote:
>
> On Wed, Feb 03, 2021 at 09:46:55AM -0800, Ivan Babrou wrote:
> > > 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 l
On Wed, Feb 03, 2021 at 09:46:55AM -0800, Ivan Babrou wrote:
> > 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.
>
> > > edfd9b7838ba5e47f
> 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 edfd9b7838ba5e
On Tue, Feb 02, 2021 at 07:09:44PM -0800, Ivan Babrou wrote:
> On Thu, Jan 28, 2021 at 7:35 PM Ivan Babrou wrote:
> > ==
> > [ 128.368523][ C0] BUG: KASAN: stack-out-of-bounds in
> > unwind_next_f
On Thu, Jan 28, 2021 at 7:35 PM Ivan Babrou wrote:
>
> Hello,
>
> We've noticed the following regression in Linux 5.10 branch:
>
> [ 128.367231][C0]
> ==
> [ 128.368523][ C0] BUG:
Hello,
We've noticed the following regression in Linux 5.10 branch:
[ 128.367231][C0]
==
[ 128.368523][ C0] BUG: KASAN: stack-out-of-bounds in
unwind_next_frame (arch/x86/kernel/unwind_orc.c:371
arch/x86/kernel/unwind_
Alex,
On Mon, 1 Apr 2019, 573149609 wrote:
> In 5.1-rc2:
> [ 66.801925] BUG: KASAN: stack-out-of-bounds in
> unwind_next_frame+0x177b/0x19e0
> [ 66.801925] Read of size 8 at addr 88806d007c50 by task
> syz-executor374/5016
> [ 66.801925] CPU: 0 PID: 5016 Comm: s
Alex,
On Mon, 25 Mar 2019, 573149609 wrote:
Thanks for the report.
> I think I found a reproducible kernel bug in version 5.0.4.
> Source file: arch/x86/kernel/unwind_orc.c:505
> The KASAN output is as following:
> [ 26.095365] BUG: KASAN: stack-out-of-bounds in
> unwind_ne
On Mon, 25 Mar 2019, Gen Zhang wrote:
> Hi,
> I think I found a reproducible kernel bug in version 5.0.4.
> Source file: arch/x86/kernel/unwind_orc.c:505
Thanks for report, but please refrain from sending the same thing over and
over. It's not adding any value.
Thanks,
tglx
Hi,
I think I found a reproducible kernel bug in version 5.0.4.
Source file: arch/x86/kernel/unwind_orc.c:505
The KASAN output is as following:
[ 26.095365] BUG: KASAN: stack-out-of-bounds in
unwind_next_frame+0x1403/0x19e0
[ 26.095365] Read of size 8 at addr 88805cc67d18 by task
syz
On Thu, Jul 19, 2018 at 10:33:47AM -0500, Josh Poimboeuf wrote:
> On Thu, Jul 19, 2018 at 01:33:54PM +0900, Prashant Bhole wrote:
> > Hi Peter, Josh,
> >
> > Found following bug. This bug can not be seen with this fix:
> > https://lkml.org/lkml/2018/5/10/280.
>
> Peter, care to clean that up and
On Thu, Jul 19, 2018 at 01:33:54PM +0900, Prashant Bhole wrote:
> Hi Peter, Josh,
>
> Found following bug. This bug can not be seen with this fix:
> https://lkml.org/lkml/2018/5/10/280.
Peter, care to clean that up and submit it?
--
Josh
Hi Peter, Josh,
Found following bug. This bug can not be seen with this fix:
https://lkml.org/lkml/2018/5/10/280.
Here unwind_next_frame+0x463 is pointing at: "*ip = regs->ip;" in
deref_stack_iret_regs().
[ 2505.084076] BUG: KASAN: stack-out-of-bounds in
unwind_next_fram
24 matches
Mail list logo
