From: Joel Fernandes <joel@joelfernandes.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Anders Roxell <anders.roxell@linaro.org>,
paulmck@kernel.org, "Naveen N . Rao" <naveen.n.rao@linux.ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
David Miller <davem@davemloft.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] kprobes: Lock rcu_read_lock() while searching kprobe
Date: Mon, 2 Dec 2019 16:08:54 -0500 [thread overview]
Message-ID: <20191202210854.GD17234@google.com> (raw)
In-Reply-To: <157527193358.11113.14859628506665612104.stgit@devnote2>
On Mon, Dec 02, 2019 at 04:32:13PM +0900, Masami Hiramatsu wrote:
> Anders reported that the lockdep warns that suspicious
> RCU list usage in register_kprobe() (detected by
> CONFIG_PROVE_RCU_LIST.) This is because get_kprobe()
> access kprobe_table[] by hlist_for_each_entry_rcu()
> without rcu_read_lock.
>
> If we call get_kprobe() from the breakpoint handler context,
> it is run with preempt disabled, so this is not a problem.
> But in other cases, instead of rcu_read_lock(), we locks
> kprobe_mutex so that the kprobe_table[] is not updated.
> So, current code is safe, but still not good from the view
> point of RCU.
>
> Let's lock the rcu_read_lock() around get_kprobe() and
> ensure kprobe_mutex is locked at those points.
>
> Note that we can safely unlock rcu_read_lock() soon after
> accessing the list, because we are sure the found kprobe has
> never gone before unlocking kprobe_mutex. Unless locking
> kprobe_mutex, caller must hold rcu_read_lock() until it
> finished operations on that kprobe.
>
> Reported-by: Anders Roxell <anders.roxell@linaro.org>
> Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
Instead of this, can you not just pass the lockdep_is_held() expression as
the last argument to list_for_each_entry_rcu() to silence the warning? Then
it will be a simpler patch.
thanks,
- Joel
> ---
> kernel/kprobes.c | 18 ++++++++++++++----
> 1 file changed, 14 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/kprobes.c b/kernel/kprobes.c
> index 53534aa258a6..fd814ea7dbd8 100644
> --- a/kernel/kprobes.c
> +++ b/kernel/kprobes.c
> @@ -319,6 +319,7 @@ static inline void reset_kprobe_instance(void)
> * - under the kprobe_mutex - during kprobe_[un]register()
> * OR
> * - with preemption disabled - from arch/xxx/kernel/kprobes.c
> + * In both cases, caller must disable preempt (or acquire rcu_read_lock)
> */
> struct kprobe *get_kprobe(void *addr)
> {
> @@ -435,6 +436,7 @@ static int kprobe_queued(struct kprobe *p)
> /*
> * Return an optimized kprobe whose optimizing code replaces
> * instructions including addr (exclude breakpoint).
> + * This must be called with locking kprobe_mutex.
> */
> static struct kprobe *get_optimized_kprobe(unsigned long addr)
> {
> @@ -442,9 +444,12 @@ static struct kprobe *get_optimized_kprobe(unsigned long addr)
> struct kprobe *p = NULL;
> struct optimized_kprobe *op;
>
> + lockdep_assert_held(&kprobe_mutex);
> + rcu_read_lock();
> /* Don't check i == 0, since that is a breakpoint case. */
> for (i = 1; !p && i < MAX_OPTIMIZED_LENGTH; i++)
> p = get_kprobe((void *)(addr - i));
> + rcu_read_unlock(); /* We are safe because kprobe_mutex is held */
>
> if (p && kprobe_optready(p)) {
> op = container_of(p, struct optimized_kprobe, kp);
> @@ -1478,18 +1483,21 @@ static struct kprobe *__get_valid_kprobe(struct kprobe *p)
> {
> struct kprobe *ap, *list_p;
>
> + lockdep_assert_held(&kprobe_mutex);
> + rcu_read_lock();
> ap = get_kprobe(p->addr);
> if (unlikely(!ap))
> - return NULL;
> + goto out;
>
> if (p != ap) {
> list_for_each_entry_rcu(list_p, &ap->list, list)
> if (list_p == p)
> /* kprobe p is a valid probe */
> - goto valid;
> - return NULL;
> + goto out;
> + ap = NULL;
> }
> -valid:
> +out:
> + rcu_read_unlock(); /* We are safe because kprobe_mutex is held */
> return ap;
> }
>
> @@ -1602,7 +1610,9 @@ int register_kprobe(struct kprobe *p)
>
> mutex_lock(&kprobe_mutex);
>
> + rcu_read_lock();
> old_p = get_kprobe(p->addr);
> + rcu_read_unlock(); /* We are safe because kprobe_mutex is held */
> if (old_p) {
> /* Since this may unoptimize old_p, locking text_mutex. */
> ret = register_aggr_kprobe(old_p, p);
>
next prev parent reply other threads:[~2019-12-02 21:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 7:32 [PATCH -tip] kprobes: Lock rcu_read_lock() while searching kprobe Masami Hiramatsu
2019-12-02 15:17 ` Anders Roxell
2019-12-02 21:08 ` Joel Fernandes [this message]
2019-12-02 22:34 ` Masami Hiramatsu
2019-12-02 23:35 ` Joel Fernandes
2019-12-03 6:02 ` Masami Hiramatsu
2019-12-03 7:13 ` Ingo Molnar
2019-12-03 17:57 ` Paul E. McKenney
2019-12-04 10:05 ` Ingo Molnar
2019-12-04 16:12 ` Paul E. McKenney
2019-12-05 4:19 ` Masami Hiramatsu
2019-12-06 1:11 ` Joel Fernandes
2019-12-06 3:11 ` Paul E. McKenney
2019-12-08 0:08 ` Joel Fernandes
2019-12-09 3:39 ` Paul E. McKenney
2019-12-17 14:59 ` Masami Hiramatsu
2019-12-17 18:07 ` Joel Fernandes
2019-12-04 4:09 ` Joel Fernandes
2019-12-04 4:20 ` Joel Fernandes
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=20191202210854.GD17234@google.com \
--to=joel@joelfernandes.org \
--cc=anders.roxell@linaro.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=paulmck@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox