mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Muchun Song <songmuchun@bytedance.com>, Ingo Molnar <mingo@kernel.org>
Cc: naveen.n.rao@linux.ibm.com, anil.s.keshavamurthy@intel.com,
	davem@davemloft.net, songliubraving@fb.com,
	LKML <linux-kernel@vger.kernel.org>,
	Chengming Zhou <zhouchengming@bytedance.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] kprobes: Fix kill kprobe which has been marked as gone
Date: Wed, 2 Sep 2020 12:05:44 +0900	[thread overview]
Message-ID: <20200902120544.d839e3a9236696978ca87723@kernel.org> (raw)
In-Reply-To: <CAMZfGtVTTZ1XZ2sLERpjevGmSO+8ex4PdfPaWLFh7Ro2r5oYYA@mail.gmail.com>

Hi Ingo,

Could you merge this fix to -tip?

I can resend it with other kprobes fixes.

Hi Muchun,

We also need;

Cc: stable@vger.kernel.org

for bugfix so that the patch can be backported correctly after merged to upstream.

Thank you,

On Mon, 31 Aug 2020 10:59:19 +0800
Muchun Song <songmuchun@bytedance.com> wrote:

> Cc Andrew and Steven.
> 
> Any other comments or someone can add this to the queue for the
> merge window? It's worth fixing it.
> 
> On Sat, Aug 22, 2020 at 11:01 AM 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.
> >
> > Fixes: e8386a0cb22f ("kprobes: support probing module __exit function")
> > Signed-off-by: Muchun Song <songmuchun@bytedance.com>
> > Co-developed-by: Chengming Zhou <zhouchengming@bytedance.com>
> > Signed-off-by: Chengming Zhou <zhouchengming@bytedance.com>
> > Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
> > ---
> > changelogs in v2:
> >  1. Add a WARN_ON_ONCE in the kill_kprobe() to catch incorrect use of it.
> >  2. Update 'Fixes' tag in the commmit log.
> >
> >  kernel/kprobes.c | 9 ++++++++-
> >  1 file changed, 8 insertions(+), 1 deletion(-)
> >
> > diff --git a/kernel/kprobes.c b/kernel/kprobes.c
> > index d36e2b017588..9348b0c36ae0 100644
> > --- a/kernel/kprobes.c
> > +++ b/kernel/kprobes.c
> > @@ -2143,6 +2143,9 @@ static void kill_kprobe(struct kprobe *p)
> >
> >         lockdep_assert_held(&kprobe_mutex);
> >
> > +       if (WARN_ON_ONCE(kprobe_gone(p)))
> > +               return;
> > +
> >         p->flags |= KPROBE_FLAG_GONE;
> >         if (kprobe_aggrprobe(p)) {
> >                 /*
> > @@ -2422,7 +2425,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 +2445,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
> >
> 
> 
> --
> Yours,
> Muchun


-- 
Masami Hiramatsu <mhiramat@kernel.org>

  reply	other threads:[~2020-09-02  3:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-22  3:00 Muchun Song
2020-08-31  2:59 ` Muchun Song
2020-09-02  3:05   ` Masami Hiramatsu [this message]
2020-09-02  3:15     ` [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=20200902120544.d839e3a9236696978ca87723@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=naveen.n.rao@linux.ibm.com \
    --cc=rostedt@goodmis.org \
    --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

all inboxes | Powered by JetHome®