From: Yonghong Song <yhs@fb.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: <mingo@kernel.org>, <tglx@linutronix.de>, <peterz@infradead.org>,
<linux-kernel@vger.kernel.org>, <x86@kernel.org>,
<netdev@vger.kernel.org>, <ast@fb.com>, <kernel-team@fb.com>
Subject: Re: [PATCH][v3] uprobes/x86: emulate push insns for uprobe on x86
Date: Tue, 14 Nov 2017 14:43:32 -0800 [thread overview]
Message-ID: <946788b4-e57b-c7c2-9ba8-3c6fe87c4af8@fb.com> (raw)
In-Reply-To: <20171114160304.GA19323@redhat.com>
On 11/14/17 8:03 AM, Oleg Nesterov wrote:
> On 11/14, Oleg Nesterov wrote:
>>
>>> +#ifdef CONFIG_X86_64
>>> + if (test_thread_flag(TIF_ADDR32))
>>> + return -ENOSYS;
>>> +#endif
>>
>> No, this doesn't look right, see my previous email. You should do this
>> check in the "if (insn->length == 2)" branch below, "push bp" should be
>> emulated correctly.
>>
>> And test_thread_flag(TIF_ADDR32) is not right too. The caller is not
>> necessarily the probed task. See is_64bit_mm(mm) in arch_uprobe_analyze_insn().
>>
>> And again... please check if uprobe_init_insn() fails or not in this case
>> (32bit task does, say, "push r8"). If it fails, your V2 should be fine.
>>
>>
>> To remind, uprobes && 32-bit is broken, let me quote my another email:
>>
>> The 3rd bug means that you simply can't uprobe a 32bit task on a 64bit
>> system, the in_compat_syscall() logic in get_unmapped_area() looks very
>> wrong although I need to re-check.
>
> Yes,
>
>> I didn't have time for this problem so far. But emulation should work, so
>> you can hopefully test your patch.
>
> Ah, no, sizeof_long() is broken by the same reason, so you can't test it...
Right. I hacked the emulate_push_stack (original name: push_ret_address)
with sizeof_long = 4, and 32bit binary uprobe works fine on x86_64
platform then... But that will involve a bigger change to propogate
the is_64bit_mm() along the call graph.
>
> OK, I'll try to do something tomorrow, then we will see what can we do
> with your patch...
Thanks for reviewing! I will wait for your further comments/direction
before next step.
>
> But it would be nice if you can check what uprobe_init_insn() does in this
> case, see above.
As mentioned in my previous email, for 32bit application,
compiler won't generate "push %r8" as "%r8" is only available on
x86_64 platform. For 32bit app, I see "push %bp" etc which does not
have rex_prefix. They cannot be emulated right now due to
emulate_push_stack needs change.
>
> Oleg.
>
next prev parent reply other threads:[~2017-11-14 22:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 22:11 Yonghong Song
2017-11-14 15:51 ` Oleg Nesterov
2017-11-14 16:03 ` Oleg Nesterov
2017-11-14 22:43 ` Yonghong Song [this message]
2017-11-15 15:47 ` Oleg Nesterov
2017-11-15 17:07 ` Oleg Nesterov
2017-11-15 17:25 ` Yonghong Song
2017-11-14 22:35 ` Yonghong Song
2017-11-15 15:38 ` Oleg Nesterov
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=946788b4-e57b-c7c2-9ba8-3c6fe87c4af8@fb.com \
--to=yhs@fb.com \
--cc=ast@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®