Linux kernel debug - RIP and RSP points to same address range

6 views
Skip to first unread message

Tony Mathew

unread,
Mar 1, 2024, 8:00:04 AM3/1/24
to inside...@googlegroups.com
Hi All,

This is with respect to a linux kernel crash. 

Can someone tell me a scenario where  an RIP value is in the range os RSP's address?  Example RIP: 0xffffbe63d67937e0 and RSP: 0xffffbe63d6793798? . Usually RIP will be pointing to the text section that will have a different address range than that of stack pointer. 

**I don't have the crash dump with me**. I was asked this question by another person.

Regards,
Mathew

Anil Kumar Pugalia

unread,
Mar 1, 2024, 11:21:00 PM3/1/24
to inside...@googlegroups.com

Many reasons. But basically, some corruption in pointer values. For example, if there is call to a function through invalid function pointer. Or, buffer overflow causing an invalid address load in stack pointer, etc.

Regards
Anil
Passion: https://sysplay.in (Playing with Systems)
Tony Mathew wrote on 01/03/24 6:29 pm:
--
You received this message because you are subscribed to the Google Groups "SysPlay's Inside Linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to inside_linux...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/inside_linux/CAAaR2_Lv5uN%2BFNOKYd5RTZ7ocS5_BnFU1Vo45guQ-e00RT3%2BMA%40mail.gmail.com.

Tony Mathew

unread,
Mar 5, 2024, 2:09:53 AM3/5/24
to inside...@googlegroups.com
Hi Anil Sir,

Right, I think may be some stack corruption. Hard to debug this as no "Call Trace:" printed.
Thanks!

Regards,
Tony

Anil Kumar Pugalia

unread,
Mar 9, 2024, 12:41:40 AM3/9/24
to inside...@googlegroups.com

Try to step through before the crash.

Regards
Anil
Passion: https://sysplay.in (Playing with Systems)
Tony Mathew wrote on 05/03/24 12:39 pm:
Reply all
Reply to author
Forward
0 new messages