From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>, Denys Vlasenko <dvlasenk@redhat.com>,
Hugh Dickins <hughd@google.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uprobes: Shift ->readpage check from __copy_insn() to uprobe_register()
Date: Wed, 21 May 2014 14:23:35 +0530 [thread overview]
Message-ID: <20140521085335.GA29630@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140519184054.GA6750@redhat.com>
* Oleg Nesterov <oleg@redhat.com> [2014-05-19 20:40:54]:
> Sorry for double-posting, but it seems that this patch didn't reach
> lkml. Let me resend it just on case. Plus another patch in reply, on
> top of this change.
>
> -------------------------------------------------------------------------------
> Subject: [PATCH] uprobes: Shift ->readpage check from __copy_insn() to uprobe_register()
>
> copy_insn() fails with -EIO if ->readpage == NULL, but this error
> is not propagated unless uprobe_register() path finds ->mm which
> already mmaps this file. In this case (say) "perf record" does not
> actually install the probe, but the user can't know about this.
>
> Move this check into uprobe_register() so that this problem can be
> detected earlier and reported to user.
>
> Note: this is still not perfect,
>
> - copy_insn() and arch_uprobe_analyze_insn() should be called
> by uprobe_register() but this is not simple, we need vm_file
> for read_mapping_page() (although perhaps we can pass NULL),
> and we need ->mm for is_64bit_mm() (although this logic is
> broken anyway).
>
> - uprobe_register() should be called by create_trace_uprobe(),
> not by probe_event_enable(), so that an error can be detected
> at "perf probe -x" time. This also needs more changes in the
> core uprobe code, uprobe register/unregister interface was
> poorly designed from the very beginning.
>
> Reported-by: Denys Vlasenko <dvlasenk@redhat.com>
> Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Acked-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
--
Thanks and Regards
Srikar Dronamraju
next prev parent reply other threads:[~2014-05-21 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 18:40 [PATCH] uprobes: Shift ->readpage check from __copy_insn() to uprobe_register() Oleg Nesterov
2014-05-19 18:41 ` [PATCH] uprobes: Teach copy_insn() to support tmpfs Oleg Nesterov
2014-05-21 8:54 ` Srikar Dronamraju
2014-06-05 14:39 ` [tip:perf/core] " tip-bot for Oleg Nesterov
2014-05-21 8:53 ` Srikar Dronamraju [this message]
2014-06-05 14:38 ` [tip:perf/core] uprobes: Shift ->readpage check from __copy_insn( ) to uprobe_register() tip-bot for 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=20140521085335.GA29630@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=dvlasenk@redhat.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.