mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Muchun Song <songmuchun@bytedance.com>,
	naveen.n.rao@linux.ibm.com, anil.s.keshavamurthy@intel.com,
	davem@davemloft.net, songliubraving@fb.com,
	linux-kernel@vger.kernel.org,
	Chengming Zhou <zhouchengming@bytedance.com>
Subject: Re: [PATCH] kprobes: Fix kill kprobe which has been marked as gone
Date: Fri, 21 Aug 2020 22:28:47 +0900	[thread overview]
Message-ID: <20200821222847.7d0730e4b193c3ea8da6bae2@kernel.org> (raw)
In-Reply-To: <20200821212843.180dc6f2f417e60cff2b886c@kernel.org>

On Fri, 21 Aug 2020 21:28:43 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:

> Hi Muchun,
> 
> On Thu, 20 Aug 2020 11:19:33 +0800
> Muchun Song <songmuchun@bytedance.com> wrote:
> 
> > If a kprobe is marked as gone, we should not kill it again. Otherwise,
> > we can disarm the kprobe more than once. In that case, the statistics
> > of kprobe_ftrace_enabled can unbalance which can lead to that kprobe
> > do not work.
> > 
> 
> Good catch! Hmm, I think we also need an assertion in
> kill_kprobe() so that p is already gone. Anyway, this looks good to me.
> 
> Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
> 
> Thanks!
> 
> > Fixes: 0cb2f1372baa ("kprobes: Fix NULL pointer dereference at kprobe_ftrace_handler")

BTW, this fixes older bug than this commit.

Fixes: e8386a0cb22f ("kprobes: support probing module __exit function")

Thank you,

> > Signed-off-by: Muchun Song <songmuchun@bytedance.com>
> > Co-developed-by: Chengming Zhou <zhouchengming@bytedance.com>
> > Signed-off-by: Chengming Zhou <zhouchengming@bytedance.com>
> > ---
> >  kernel/kprobes.c | 6 +++++-
> >  1 file changed, 5 insertions(+), 1 deletion(-)
> > 
> > diff --git a/kernel/kprobes.c b/kernel/kprobes.c
> > index d36e2b017588..7bac3ea44ff4 100644
> > --- a/kernel/kprobes.c
> > +++ b/kernel/kprobes.c
> > @@ -2422,7 +2422,10 @@ static int kprobes_module_callback(struct notifier_block *nb,
> >  	mutex_lock(&kprobe_mutex);
> >  	for (i = 0; i < KPROBE_TABLE_SIZE; i++) {
> >  		head = &kprobe_table[i];
> > -		hlist_for_each_entry(p, head, hlist)
> > +		hlist_for_each_entry(p, head, hlist) {
> > +			if (kprobe_gone(p))
> > +				continue;
> > +
> >  			if (within_module_init((unsigned long)p->addr, mod) ||
> >  			    (checkcore &&
> >  			     within_module_core((unsigned long)p->addr, mod))) {
> > @@ -2439,6 +2442,7 @@ static int kprobes_module_callback(struct notifier_block *nb,
> >  				 */
> >  				kill_kprobe(p);
> >  			}
> > +		}
> >  	}
> >  	if (val == MODULE_STATE_GOING)
> >  		remove_module_kprobe_blacklist(mod);
> > -- 
> > 2.11.0
> > 
> 
> 
> -- 
> Masami Hiramatsu <mhiramat@kernel.org>


-- 
Masami Hiramatsu <mhiramat@kernel.org>

  reply	other threads:[~2020-08-21 13:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20  3:19 Muchun Song
2020-08-21 12:28 ` Masami Hiramatsu
2020-08-21 13:28   ` Masami Hiramatsu [this message]
2020-08-22  2:31     ` [External] " Muchun 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=20200821222847.7d0730e4b193c3ea8da6bae2@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naveen.n.rao@linux.ibm.com \
    --cc=songliubraving@fb.com \
    --cc=songmuchun@bytedance.com \
    --cc=zhouchengming@bytedance.com \
    /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

Powered by JetHome