From: Steven Rostedt <rostedt@goodmis.org>
To: Song Liu <songliubraving@fb.com>
Cc: <linux-kernel@vger.kernel.org>, <kernel-team@fb.com>,
Ingo Molnar <mingo@redhat.com>,
Howard McLauchlan <hmclauchlan@fb.com>,
Josef Bacik <jbacik@fb.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: [PATCH v3 2/2] tracing: remove igrab() iput() call from uprobes.c
Date: Fri, 20 Apr 2018 13:50:56 -0400 [thread overview]
Message-ID: <20180420135056.31bff483@gandalf.local.home> (raw)
In-Reply-To: <20180420165625.129593-2-songliubraving@fb.com>
On Fri, 20 Apr 2018 09:56:25 -0700
Song Liu <songliubraving@fb.com> wrote:
> Caller of uprobe_register is required to keep the inode and containing
> mount point referenced.
I would add a little more background to why this is the case. Also a
possible link to the conversation?
Link: http://lkml.kernel.org/r/CAELBmZB2XX=qEOLAdvGG4cPx4GEntcSnWQquJLUK1ongRj35cA@mail.gmail.com
?
-- Steve
>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Howard McLauchlan <hmclauchlan@fb.com>
> Cc: Josef Bacik <jbacik@fb.com>
> Cc: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
> Cc: Miklos Szeredi <miklos@szeredi.hu>
> Signed-off-by: Song Liu <songliubraving@fb.com>
> ---
> kernel/events/uprobes.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/events/uprobes.c b/kernel/events/uprobes.c
> index ce6848e..20486bb 100644
> --- a/kernel/events/uprobes.c
> +++ b/kernel/events/uprobes.c
> @@ -491,7 +491,6 @@ static struct uprobe *alloc_uprobe(struct inode *inode, loff_t offset)
> if (!uprobe)
> return NULL;
>
> - uprobe->inode = igrab(inode);
> uprobe->offset = offset;
> init_rwsem(&uprobe->register_rwsem);
> init_rwsem(&uprobe->consumer_rwsem);
> @@ -502,7 +501,6 @@ static struct uprobe *alloc_uprobe(struct inode *inode, loff_t offset)
> if (cur_uprobe) {
> kfree(uprobe);
> uprobe = cur_uprobe;
> - iput(inode);
> }
>
> return uprobe;
> @@ -701,7 +699,6 @@ static void delete_uprobe(struct uprobe *uprobe)
> rb_erase(&uprobe->rb_node, &uprobes_tree);
> spin_unlock(&uprobes_treelock);
> RB_CLEAR_NODE(&uprobe->rb_node); /* for uprobe_is_active() */
> - iput(uprobe->inode);
> put_uprobe(uprobe);
> }
>
> @@ -873,7 +870,8 @@ static void __uprobe_unregister(struct uprobe *uprobe, struct uprobe_consumer *u
> * tuple). Creation refcount stops uprobe_unregister from freeing the
> * @uprobe even before the register operation is complete. Creation
> * refcount is released when the last @uc for the @uprobe
> - * unregisters.
> + * unregisters. Caller of uprobe_register() is required to keep @inode
> + * (and the containing mount) referenced.
> *
> * Return errno if it cannot successully install probes
> * else return 0 (success)
next prev parent reply other threads:[~2018-04-20 17:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 16:56 [PATCH v3 1/2] tracing: fix bad use of igrab in trace_uprobe.c Song Liu
2018-04-20 16:56 ` [PATCH v3 2/2] tracing: remove igrab() iput() call from uprobes.c Song Liu
2018-04-20 17:50 ` Steven Rostedt [this message]
2018-04-23 10:03 ` Miklos Szeredi
2018-04-23 11:23 ` Song Liu
2018-04-20 18:30 ` [PATCH v3 1/2] tracing: fix bad use of igrab in trace_uprobe.c Steven Rostedt
2018-04-23 9:56 ` Miklos Szeredi
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=20180420135056.31bff483@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=hmclauchlan@fb.com \
--cc=jbacik@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mingo@redhat.com \
--cc=songliubraving@fb.com \
--cc=srikar@linux.vnet.ibm.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®