StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>There are at least two approaches. </p> <h1>Approach 1: Jprobes</h1> <p>Probably the most easy one: if <em>Jprobes</em> are suitable for your task, you could give them a try. They are the close relatives of kprobes (see their detailed description and links to the examples in the <a href="http://www.mjmwired.net/kernel/Documentation/kprobes.txt">kernel docs</a>). </p> <p>Jprobes allow to call your function with the same signature as the probed one on entry to the latter. You get all of the arguments automatically this way.</p> <h1>Approach 2: Registers and Stack</h1> <p>Another approach could be to extend a bit what you already do and retrieve the arguments from the registers and the stack. From the output log in your question, I assume you are working on a 32 bit x86 system. </p> <h2>x86, 32 bit</h2> <p>As far as I have seen, there are two most common conventions on argument passing in the Linux kernel on x86 (the details are available in the <a href="http://www.agner.org/optimize/calling_conventions.pdf">manual by Agner Fog</a>). Note that system calls follow other conventions (see the <a href="http://www.agner.org/optimize/calling_conventions.pdf">manual</a> for details) but I assume you are interested in analysing an "ordinary" function rather than a system call.</p> <h3>Convention 1</h3> <p>For the functions marked with <code>asmlinkage</code> as well as for the functions with variable argument lists, all parameters are passed on stack. The return address of the function should be at the top of the stack on entry to the function, the first parameter being located right below it. The second parameter is below the first one, and so on. </p> <p>As you have the saved value of <code>esp</code>, you can find what it points to. <code>*(esp+4)</code> should be the first argument, <code>*(esp+8)</code> - the second one, etc., if this convention is used.</p> <h3>Convention 2</h3> <p>It seems to be used for the most of the kernel functions including the one you mentioned in the question. </p> <p>The kernel is compiled with <code>-mregparm=3</code> and therefore the first 3 arguments are passed in <code>eax</code>, <code>edx</code> and <code>ecx</code>, in that order, the rest go on stack. <code>*(esp+4)</code> should be the 4th argument, <code>*(esp+8)</code> - the 5th one, and so on.</p> <h2>x86, 64bit</h2> <p>It seems that things are a bit simpler on x86-64. Most of the kernel functions (including those with variable argument list) get the first 6 arguments in <code>rdi</code>, <code>rsi</code>, <code>rdx</code>, <code>rcx</code>, <code>r8</code>, <code>r9</code>, in that order, the remaining ones go on stack. <code>*(esp+8)</code> should be the 7th argument, <code>*(esp+16)</code> - the 8th and so on.</p> <p><strong>EDIT:</strong> </p> <p>Note that on x86-32, the value of <code>esp</code> is not saved in <code>pt_regs</code> for kernel-mode traps (including the software breakpoints that KProbes rely upon). <a href="http://lxr.free-electrons.com/source/arch/x86/include/asm/ptrace.h"><asm/ptrace.h></a> provides <code>kernel_stack_pointer()</code> function to retrieve the correct value of <code>esp</code>, it works both on x86-32 and on x86-64. See the description of <code>kernel_stack_pointer()</code> in that header file for details.</p> <p>In addition, <code>regs_get_kernel_stack_nth()</code> (also defined in that header) provides a convenient way to get the contents of the stack in the handler.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload