From: zhouchengming <zhouchengming1@huawei.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: <ananth@linux.vnet.ibm.com>, <anil.s.keshavamurthy@intel.com>,
<davem@davemloft.net>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] kprobes: avoid the kprobe being re-registered
Date: Fri, 27 Oct 2017 14:16:59 +0800 [thread overview]
Message-ID: <59F2CF5B.3030507@huawei.com> (raw)
In-Reply-To: <20171027145721.ef28a8eea41210f05c23f30e@kernel.org>
On 2017/10/27 13:57, Masami Hiramatsu wrote:
> On Fri, 27 Oct 2017 09:56:40 +0800
> Zhou Chengming<zhouchengming1@huawei.com> wrote:
>
>> Changes from v1:
>> - We should put the modifies of the kprobe after the re-reg check.
>> - And then the address_safe check.
>> - When check_kprobe_address_safe() return fail, the *probed_mod
>> should be set to NULL, and no module refcount held.
> Could you split this item from this patch (with initializing probe_mod = NULL),
> since it is another bug?
>
> Thank you,
Ok, it seems more reasonable. I will split this patch into two patches later.
Thank you.
>> Old code use check_kprobe_rereg() to check if the kprobe has been
>> registered already, but check_kprobe_rereg() will release the
>> kprobe_mutex then, so maybe two paths will pass the check and
>> register the same kprobe. This patch put the check inside the mutex.
>>
>> Signed-off-by: Zhou Chengming<zhouchengming1@huawei.com>
>> ---
>> kernel/kprobes.c | 28 +++++++++-------------------
>> 1 file changed, 9 insertions(+), 19 deletions(-)
>>
>> diff --git a/kernel/kprobes.c b/kernel/kprobes.c
>> index a1606a4..f622639 100644
>> --- a/kernel/kprobes.c
>> +++ b/kernel/kprobes.c
>> @@ -1443,19 +1443,6 @@ static struct kprobe *__get_valid_kprobe(struct kprobe *p)
>> return ap;
>> }
>>
>> -/* Return error if the kprobe is being re-registered */
>> -static inline int check_kprobe_rereg(struct kprobe *p)
>> -{
>> - int ret = 0;
>> -
>> - mutex_lock(&kprobe_mutex);
>> - if (__get_valid_kprobe(p))
>> - ret = -EINVAL;
>> - mutex_unlock(&kprobe_mutex);
>> -
>> - return ret;
>> -}
>> -
>> int __weak arch_check_ftrace_location(struct kprobe *p)
>> {
>> unsigned long ftrace_addr;
>> @@ -1501,6 +1488,7 @@ static int check_kprobe_address_safe(struct kprobe *p,
>> * its code to prohibit unexpected unloading.
>> */
>> if (unlikely(!try_module_get(*probed_mod))) {
>> + *probed_mod = NULL;
>> ret = -ENOENT;
>> goto out;
>> }
>> @@ -1536,9 +1524,13 @@ int register_kprobe(struct kprobe *p)
>> return PTR_ERR(addr);
>> p->addr = addr;
>>
>> - ret = check_kprobe_rereg(p);
>> - if (ret)
>> - return ret;
>> + mutex_lock(&kprobe_mutex);
>> +
>> + /* Return error if the kprobe is being re-registered */
>> + if (__get_valid_kprobe(p)) {
>> + ret = -EINVAL;
>> + goto out;
>> + }
>>
>> /* User can pass only KPROBE_FLAG_DISABLED to register_kprobe */
>> p->flags&= KPROBE_FLAG_DISABLED;
>> @@ -1547,9 +1539,7 @@ int register_kprobe(struct kprobe *p)
>>
>> ret = check_kprobe_address_safe(p,&probed_mod);
>> if (ret)
>> - return ret;
>> -
>> - mutex_lock(&kprobe_mutex);
>> + goto out;
>>
>> old_p = get_kprobe(p->addr);
>> if (old_p) {
>> --
>> 1.8.3.1
>>
>
prev parent reply other threads:[~2017-10-27 6:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 1:56 [PATCH v2] kprobes: avoid the kprobe being re-registered Zhou Chengming
2017-10-27 5:57 ` Masami Hiramatsu
2017-10-27 6:16 ` zhouchengming [this message]
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=59F2CF5B.3030507@huawei.com \
--to=zhouchengming1@huawei.com \
--cc=ananth@linux.vnet.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@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 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.