Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: peterz at infradead.org (Peter Zijlstra)
Subject: [PATCH 2/4] x86/kprobes: Fix frame pointer annotations
Date: Thu, 9 May 2019 19:18:40 +0200	[thread overview]
Message-ID: <20190509171840.GZ2623@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <81170F0B-A2BB-4CD6-A1B5-5E7E0DDBC282@amacapital.net>

On Thu, May 09, 2019 at 09:20:06AM -0700, Andy Lutomirski wrote:
> > +ENTRY(call_to_exception_trampoline)
> > +    /*
> > +     * On entry the stack looks like:
> > +     *
> > +     *   2*4(%esp) <previous context>
> > +     *   1*4(%esp) RET-IP
> > +     *   0*4(%esp) func
> > +     *
> > +     * transform this into:
> > +     *
> > +     *  19*4(%esp) <previous context>
> > +     *  18*4(%esp) gap / RET-IP
> > +     *  17*4(%esp) gap / func
> > +     *  16*4(%esp) ss
> > +     *  15*4(%esp) sp / <previous context>
> > +     *  14*4(%esp) flags
> > +     *  13*4(%esp) cs
> > +     *  12*4(%esp) ip / RET-IP
> > +     *  11*4(%esp) orig_eax
> > +     *  10*4(%esp) gs
> > +     *   9*4(%esp) fs
> > +     *   8*4(%esp) es
> > +     *   7*4(%esp) ds
> > +     *   6*4(%esp) eax
> > +     *   5*4(%esp) ebp
> > +     *   4*4(%esp) edi
> > +     *   3*4(%esp) esi
> > +     *   2*4(%esp) edx
> > +     *   1*4(%esp) ecx
> > +     *   0*4(%esp) ebx
> > +     */
> > +    pushl    %ss
> > +    pushl    %esp        # points at ss
> > +    addl    $3*4, (%esp)    #   point it at <previous context>
> > +    pushfl
> > +    pushl    %cs
> > +    pushl    5*4(%esp)    # RET-IP
> > +    subl    5, (%esp)    #   point at CALL instruction
> > +    pushl    $-1
> > +    pushl    %gs
> > +    pushl    %fs
> > +    pushl    %es
> > +    pushl    %ds
> > +    pushl    %eax
> > +    pushl    %ebp
> > +    pushl    %edi
> > +    pushl    %esi
> > +    pushl    %edx
> > +    pushl    %ecx
> > +    pushl    %ebx
> > +
> > +    ENCODE_FRAME_POINTER
> > +
> > +    movl    %esp, %eax    # 1st argument: pt_regs
> > +
> > +    movl    17*4(%esp), %ebx    # func
> > +    CALL_NOSPEC %ebx
> > +
> > +    movl    PT_OLDESP(%esp), %eax
> > +
> > +    movl    PT_EIP(%esp), %ecx
> > +    movl    %ecx, -1*4(%eax)
> > +
> > +    movl    PT_EFLAGS(%esp), %ecx
> > +    movl    %ecx, -2*4(%eax)
> > +
> > +    movl    PT_EAX(%esp), %ecx
> > +    movl    %ecx, -3*4(%eax)
> > +
> > +    popl    %ebx
> > +    popl    %ecx
> > +    popl    %edx
> > +    popl    %esi
> > +    popl    %edi
> > +    popl    %ebp
> > +
> > +    lea    -3*4(%eax), %esp
> > +    popl    %eax
> > +    popfl
> > +    ret
> > +END(call_to_exception_trampoline)

> Potentially minor nit: you’re doing popfl, but you’re not doing
> TRACE_IRQ_whatever.  This makes me think that you should either add
> the tracing (ugh!) or you should maybe just skip the popfl.

Yeah, so we really should not change flags I suppose. If this lives I'll
remove the popfl.

WARNING: multiple messages have this Message-ID (diff)
From: peterz@infradead.org (Peter Zijlstra)
Subject: [PATCH 2/4] x86/kprobes: Fix frame pointer annotations
Date: Thu, 9 May 2019 19:18:40 +0200	[thread overview]
Message-ID: <20190509171840.GZ2623@hirez.programming.kicks-ass.net> (raw)
Message-ID: <20190509171840.V10aAN0wUAWNa_LsdQIZKP9B1Emkpa8utfx9OVFMzjE@z> (raw)
In-Reply-To: <81170F0B-A2BB-4CD6-A1B5-5E7E0DDBC282@amacapital.net>

On Thu, May 09, 2019@09:20:06AM -0700, Andy Lutomirski wrote:
> > +ENTRY(call_to_exception_trampoline)
> > +    /*
> > +     * On entry the stack looks like:
> > +     *
> > +     *   2*4(%esp) <previous context>
> > +     *   1*4(%esp) RET-IP
> > +     *   0*4(%esp) func
> > +     *
> > +     * transform this into:
> > +     *
> > +     *  19*4(%esp) <previous context>
> > +     *  18*4(%esp) gap / RET-IP
> > +     *  17*4(%esp) gap / func
> > +     *  16*4(%esp) ss
> > +     *  15*4(%esp) sp / <previous context>
> > +     *  14*4(%esp) flags
> > +     *  13*4(%esp) cs
> > +     *  12*4(%esp) ip / RET-IP
> > +     *  11*4(%esp) orig_eax
> > +     *  10*4(%esp) gs
> > +     *   9*4(%esp) fs
> > +     *   8*4(%esp) es
> > +     *   7*4(%esp) ds
> > +     *   6*4(%esp) eax
> > +     *   5*4(%esp) ebp
> > +     *   4*4(%esp) edi
> > +     *   3*4(%esp) esi
> > +     *   2*4(%esp) edx
> > +     *   1*4(%esp) ecx
> > +     *   0*4(%esp) ebx
> > +     */
> > +    pushl    %ss
> > +    pushl    %esp        # points at ss
> > +    addl    $3*4, (%esp)    #   point it at <previous context>
> > +    pushfl
> > +    pushl    %cs
> > +    pushl    5*4(%esp)    # RET-IP
> > +    subl    5, (%esp)    #   point at CALL instruction
> > +    pushl    $-1
> > +    pushl    %gs
> > +    pushl    %fs
> > +    pushl    %es
> > +    pushl    %ds
> > +    pushl    %eax
> > +    pushl    %ebp
> > +    pushl    %edi
> > +    pushl    %esi
> > +    pushl    %edx
> > +    pushl    %ecx
> > +    pushl    %ebx
> > +
> > +    ENCODE_FRAME_POINTER
> > +
> > +    movl    %esp, %eax    # 1st argument: pt_regs
> > +
> > +    movl    17*4(%esp), %ebx    # func
> > +    CALL_NOSPEC %ebx
> > +
> > +    movl    PT_OLDESP(%esp), %eax
> > +
> > +    movl    PT_EIP(%esp), %ecx
> > +    movl    %ecx, -1*4(%eax)
> > +
> > +    movl    PT_EFLAGS(%esp), %ecx
> > +    movl    %ecx, -2*4(%eax)
> > +
> > +    movl    PT_EAX(%esp), %ecx
> > +    movl    %ecx, -3*4(%eax)
> > +
> > +    popl    %ebx
> > +    popl    %ecx
> > +    popl    %edx
> > +    popl    %esi
> > +    popl    %edi
> > +    popl    %ebp
> > +
> > +    lea    -3*4(%eax), %esp
> > +    popl    %eax
> > +    popfl
> > +    ret
> > +END(call_to_exception_trampoline)

> Potentially minor nit: you’re doing popfl, but you’re not doing
> TRACE_IRQ_whatever.  This makes me think that you should either add
> the tracing (ugh!) or you should maybe just skip the popfl.

Yeah, so we really should not change flags I suppose. If this lives I'll
remove the popfl.

  parent reply	other threads:[~2019-05-09 17:18 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-08  7:49 [PATCH 0/4] x86: int3 fallout peterz
2019-05-08  7:49 ` Peter Zijlstra
2019-05-08  7:49 ` [PATCH 1/4] x86/entry/32: Clean up return from interrupt preemption path peterz
2019-05-08  7:49   ` Peter Zijlstra
2019-05-08  7:49 ` [PATCH 2/4] x86/kprobes: Fix frame pointer annotations peterz
2019-05-08  7:49   ` Peter Zijlstra
2019-05-08 11:54   ` jpoimboe
2019-05-08 11:54     ` Josh Poimboeuf
2019-05-08 12:04     ` peterz
2019-05-08 12:04       ` Peter Zijlstra
     [not found]       ` <20190508124248.u5ukpbhnh4wpiccq@treble>
     [not found]         ` <20190508153907.GM2589@hirez.programming.kicks-ass.net>
2019-05-08 18:48           ` jpoimboe
2019-05-08 18:48             ` Josh Poimboeuf
2019-05-09  1:20             ` mhiramat
2019-05-09  1:20               ` Masami Hiramatsu
2019-05-09  8:14               ` peterz
2019-05-09  8:14                 ` Peter Zijlstra
2019-05-09  9:27                 ` peterz
2019-05-09  9:27                   ` Peter Zijlstra
2019-05-09 14:00                 ` jpoimboe
2019-05-09 14:00                   ` Josh Poimboeuf
2019-05-09 14:01                 ` mhiramat
2019-05-09 14:01                   ` Masami Hiramatsu
2019-05-09 17:14                   ` peterz
2019-05-09 17:14                     ` Peter Zijlstra
2019-05-10  4:58                     ` mhiramat
2019-05-10  4:58                       ` Masami Hiramatsu
2019-05-10 12:31                       ` peterz
2019-05-10 12:31                         ` Peter Zijlstra
2019-05-11  0:52                         ` mhiramat
2019-05-11  0:52                           ` Masami Hiramatsu
2019-05-10 12:40                       ` peterz
2019-05-10 12:40                         ` Peter Zijlstra
2019-05-11  0:56                         ` mhiramat
2019-05-11  0:56                           ` Masami Hiramatsu
2019-05-13  8:15                           ` peterz
2019-05-13  8:15                             ` Peter Zijlstra
2019-05-09 16:20                 ` luto
2019-05-09 16:20                   ` Andy Lutomirski
2019-05-09 17:18                   ` peterz [this message]
2019-05-09 17:18                     ` Peter Zijlstra
2019-05-09 17:43                   ` rostedt
2019-05-09 17:43                     ` Steven Rostedt
2019-05-10  3:21                     ` mhiramat
2019-05-10  3:21                       ` Masami Hiramatsu
2019-05-10 12:14                       ` peterz
2019-05-10 12:14                         ` Peter Zijlstra
2019-05-10 12:17                       ` peterz
2019-05-10 12:17                         ` Peter Zijlstra
2019-05-10 14:54                         ` rostedt
2019-05-10 14:54                           ` Steven Rostedt
2019-05-09 17:37                 ` rostedt
2019-05-09 17:37                   ` Steven Rostedt
2019-05-09 18:26                   ` peterz
2019-05-09 18:26                     ` Peter Zijlstra
2019-05-09 18:36                     ` rostedt
2019-05-09 18:36                       ` Steven Rostedt
2019-05-08  7:49 ` [PATCH 3/4] x86/ftrace: Add pt_regs frame annotations peterz
2019-05-08  7:49   ` Peter Zijlstra
2019-05-08  7:49 ` [RFC][PATCH 4/4] x86_32: Provide consistent pt_regs peterz
2019-05-08  7:49   ` Peter Zijlstra
2019-05-08 11:57   ` jpoimboe
2019-05-08 11:57     ` Josh Poimboeuf
2019-05-08 20:58   ` torvalds
2019-05-08 20:58     ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190509171840.GZ2623@hirez.programming.kicks-ass.net \
    --to=linux-kselftest@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox