All of lore.kernel.org
 help / color / mirror / Atom feed
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] kprobes: avoid the kprobe being re-registered
Date: Fri, 27 Oct 2017 09:24:07 +0800	[thread overview]
Message-ID: <59F28AB7.4000300@huawei.com> (raw)
In-Reply-To: <20171026233944.d56f558c01275e70744c2add@kernel.org>

On 2017/10/26 22:39, Masami Hiramatsu wrote:
> On Thu, 26 Oct 2017 20:11:25 +0800
> Zhou Chengming<zhouchengming1@huawei.com>  wrote:
>
>> 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.
> Still no good, see below comment.
>
>> Signed-off-by: Zhou Chengming<zhouchengming1@huawei.com>
>> ---
>>   kernel/kprobes.c | 23 ++++++-----------------
>>   1 file changed, 6 insertions(+), 17 deletions(-)
>>
>> diff --git a/kernel/kprobes.c b/kernel/kprobes.c
>> index a1606a4..2a4873a 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;
>> @@ -1536,10 +1523,6 @@ int register_kprobe(struct kprobe *p)
>>   		return PTR_ERR(addr);
>>   	p->addr = addr;
>>
>> -	ret = check_kprobe_rereg(p);
>> -	if (ret)
>> -		return ret;
>> -
>>   	/* User can pass only KPROBE_FLAG_DISABLED to register_kprobe */
>>   	p->flags&= KPROBE_FLAG_DISABLED;
>>   	p->nmissed = 0;
> here, we already modifies the kprobe. We need to check and reject before modifying it.
>
> Thank you,

Ah, right. We should put the modifies after the re-reg check. I will send a patch-v2.

Thank you.

>> @@ -1551,6 +1534,12 @@ int register_kprobe(struct kprobe *p)
>>
>>   	mutex_lock(&kprobe_mutex);
>>
>> +	/* Return error if the kprobe is being re-registered */
>> +	if (__get_valid_kprobe(p)) {
>> +		ret = -EINVAL;
>> +		goto out;
>> +	}
>> +
>>   	old_p = get_kprobe(p->addr);
>>   	if (old_p) {
>>   		/* Since this may unoptimize old_p, locking text_mutex. */
>> -- 
>> 1.8.3.1
>>
>

      reply	other threads:[~2017-10-27  1:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26 12:11 [PATCH] kprobes: avoid the kprobe being re-registered Zhou Chengming
2017-10-26 14:39 ` Masami Hiramatsu
2017-10-27  1:24   ` 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=59F28AB7.4000300@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.