mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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][v4] uprobes/x86: emulate push insns for uprobe on x86
Date: Mon, 20 Nov 2017 10:25:55 -0800	[thread overview]
Message-ID: <b3b59c8a-494f-51ed-2691-c4c544e771a1@fb.com> (raw)
In-Reply-To: <20171120164145.GA2387@redhat.com>



On 11/20/17 8:41 AM, Oleg Nesterov wrote:
> On 11/17, Yonghong Song wrote:
>>
>> On 11/17/17 9:25 AM, Oleg Nesterov wrote:
>>> On 11/15, Yonghong Song wrote:
>>>>
>>>> v3 -> v4:
>>>>    . Revert most of v3 change as 32bit emulation is not really working
>>>>      on x86_64 platform as among other issues, function emulate_push_stack()
>>>>      needs to account for 32bit app on 64bit platform.
>>>>      A separate effort is ongoing to address this issue.
>>>
>>> Reviewed-by: Oleg Nesterov <oleg@redhat.com>
>>>
>>>
>>>
>>> Please test your patch with the fix below, in this particular case the
>>> TIF_IA32 check should be fine. Although this is not what we really want,
>>> we should probably use user_64bit_mode(regs) which checks ->cs. But this
>>> needs more changes and doesn't solve other problems (get_unmapped_area)
>>> so I still can't decide what should we do right now...
>>
>> I tested the below change with my patch. On x86_64, both 64bit and 32bit
>> program can be uprobe emulated properly.
> 
> Good, so your patch is fine.

Thanks!

> 
>> On x86_32, however, there is a
>> compilation error like below:
> 
> Yes, yes, when I said "in this particular case" I meant x86_64 system only.
> 
> Sorry for confusion, I asked you to test this additional change just to
> ensure that we didn't miss something and your patch has no problems with
> 32bit tasks on 64bit system, except those we need to fix anyway.

Understood. I actually tried a little to see whether I could have a 
simple way to fix 32bit compilation error without using ugly "#ifdef 
CONFIG_X86_64". Maybe is_64bit_mm is a good choice. But we could defer 
this until you have a comprehensive fix for 32bit app uprobe on 64bit 
systems as there are multiple issues for this.

> 
> Oleg.
> 

  reply	other threads:[~2017-11-20 18:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-15 17:59 Yonghong Song
2017-11-17 17:25 ` Oleg Nesterov
2017-11-17 18:12   ` Yonghong Song
2017-11-20 16:41     ` Oleg Nesterov
2017-11-20 18:25       ` Yonghong Song [this message]
2017-11-27 18:06         ` Yonghong Song

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=b3b59c8a-494f-51ed-2691-c4c544e771a1@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®