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][v2] uprobes/x86: emulate push insns for uprobe on x86
Date: Mon, 13 Nov 2017 12:32:18 -0800	[thread overview]
Message-ID: <6fdd9773-a0d0-7598-35d4-959bb3701d1b@fb.com> (raw)
In-Reply-To: <20171113125956.GA11516@redhat.com>



On 11/13/17 4:59 AM, Oleg Nesterov wrote:
> The patch looks good to me, but I have a question because I know nothing
> about insn encoding,
> 
> On 11/10, Yonghong Song wrote:
>>
>> +static int push_setup_xol_ops(struct arch_uprobe *auprobe, struct insn *insn)
>> +{
>> +	u8 opc1 = OPCODE1(insn), reg_offset = 0;
>> +
>> +	if (opc1 < 0x50 || opc1 > 0x57)
>> +		return -ENOSYS;
>> +
>> +	if (insn->length > 2)
>> +		return -ENOSYS;
>> +	if (insn->length == 2) {
>> +		/* only support rex_prefix 0x41 (x64 only) */
>> +#ifdef CONFIG_X86_64
>> +		if (insn->rex_prefix.nbytes != 1 ||
>> +		    insn->rex_prefix.bytes[0] != 0x41)
>> +			return -ENOSYS;
>> +
>> +		auprobe->push.ilen = 2;
> 
> and the "else" branch does
> 
> 		auprobe->push.ilen = 1;
> 
> you could add
> 		auprobe->push.ilen = insn->length;
> 
> at the end of push_setup_xol_ops() instead, but this is minor/cosmetic,

Will make this change in the next revision.

> 
> 
>> +		switch (opc1) {
>> +		case 0x50:
>> +			reg_offset = offsetof(struct pt_regs, r8);
>> +			break;
>> +		case 0x51:
>> +			reg_offset = offsetof(struct pt_regs, r9);
>> +			break;
>> +		case 0x52:
>> +			reg_offset = offsetof(struct pt_regs, r10);
>> +			break;
>> +		case 0x53:
>> +			reg_offset = offsetof(struct pt_regs, r11);
>> +			break;
>> +		case 0x54:
>> +			reg_offset = offsetof(struct pt_regs, r12);
>> +			break;
>> +		case 0x55:
>> +			reg_offset = offsetof(struct pt_regs, r13);
>> +			break;
>> +		case 0x56:
>> +			reg_offset = offsetof(struct pt_regs, r14);
>> +			break;
>> +		case 0x57:
>> +			reg_offset = offsetof(struct pt_regs, r15);
>> +			break;
>> +		}
>> +#else
>> +		return -ENOSYS;
>> +#endif
> 
> OK, but shouldn't we also return ENOSYS if CONFIG_X86_64=y but the probed task is 32bit?

Just tested with a 32bit app on x86 box and segfaults. Yes, we would 
need to return ENOSYS if the app is 32bit on 64bit system. I may not
be worthwhile to emulate this uncommon case.

I will use mmap_is_ia32 or a variant to test whether the app is
32bit or not. Please let me know whether this is correct approach or not.

> 
> Or in this case uprobe_init_insn(x86_64 => false) should fail and push_setup_xol_ops()
> won't be called?
> 
> Oleg.
> 

  reply	other threads:[~2017-11-13 20:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-10 17:25 Yonghong Song
2017-11-13 12:59 ` Oleg Nesterov
2017-11-13 20:32   ` Yonghong Song [this message]
2017-11-14 15:34     ` Oleg Nesterov
2017-11-14 22:22       ` 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=6fdd9773-a0d0-7598-35d4-959bb3701d1b@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®