Function report

Linux Kernel

v5.5.9

Brick Technologies Co., Ltd

Source Code:arch\x86\kernel\dumpstack.c Create Date:2022-07-28 07:34:42
Last Modify:2020-03-12 14:18:49 Copyright©Brick
home page Tree
Annotation kernel can get tool activityDownload SCCTChinese

Name:There are a couple of reasons for the 2/3rd prologue, courtesy of Linus:* In case where we don't have the exact kernel image (which, if we did, we can* simply disassemble and navigate to the RIP), the purpose of the bigger* prologue is to have more

Proto:void show_opcodes(struct pt_regs *regs, const char *loglvl)

Type:void

Parameter:

TypeParameterName
struct pt_regs *regs
const char *loglvl
99  prologue = ip - There are a couple of reasons for the 2/3rd prologue, courtesy of Linus:* In case where we don't have the exact kernel image (which, if we did, we can* simply disassemble and navigate to the RIP), the purpose of the bigger* prologue is to have more
106  bad_ip = ser_mode(regs) determines whether a register set came from user* mode && Test whether a block of memory is a valid user space address.* Returns 0 if the range is valid, nonzero otherwise.
109  If bad_ip || probe_kernel_read(): safely attempt to read from a location*@dst: pointer to the buffer that shall take the data*@src: address to read from*@size: size of the data chunk* Safely read from address @src to the buffer at @dst. If a kernel fault Then
111  printk("%sCode: Bad RIP value.\n", loglvl)
112  Else
113  printk("%sCode: %"__stringify(There are a couple of reasons for the 2/3rd prologue, courtesy of Linus:* In case where we don't have the exact kernel image (which, if we did, we can* simply disassemble and navigate to the RIP), the purpose of the bigger* prologue is to have more )"ph <%02x> %"__stringify(EPILOGUE_SIZE)"ph\n", loglvl, opcodes, opcodes[There are a couple of reasons for the 2/3rd prologue, courtesy of Linus:* In case where we don't have the exact kernel image (which, if we did, we can* simply disassemble and navigate to the RIP), the purpose of the bigger* prologue is to have more ], opcodes + There are a couple of reasons for the 2/3rd prologue, courtesy of Linus:* In case where we don't have the exact kernel image (which, if we did, we can* simply disassemble and navigate to the RIP), the purpose of the bigger* prologue is to have more + 1)
Caller
NameDescribe
show_ip