linux-kernel - Re: Error in save_stack_trace() on x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 11 May 2008 12:58:42 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	Vegard Nossum <vegard.nossum@...il.com>
CC:	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Error in save_stack_trace() on x86_64?

Vegard Nossum wrote: in userspace this trace looks correct.
> 
> No, it is happening from kernel code. As you can see from the original
> backtrace, the regs->ip (RIP) (regs taken from the very same
> do_page_fault()) points at add_uevent_var, which is a kernel function.
> 
>>  if it happens in kernel space... I wonder if the separate exception stack
>> thing
>>  is hurting us with the stacks not being properly connected...
>>  (but oopses and the like seem to come out just fine so I kinda doubt you're
>> hitting that)
>>
> 
> Thanks for looking into this.
> 

do you happen to have something that I maybe can reproduce?
(if you have that it would save me a ton of time in reproducing)
> 
> Vegard
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/