Depending on the argument 'add', uprobe_apply() may be registering or unregistering a probe. The current comment misses the description of the registration.
Signed-off-by: Zhen Lei <thunder.leiz...@huawei.com> --- kernel/events/uprobes.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/events/uprobes.c b/kernel/events/uprobes.c index 73cc47708679f0c..c9de255e56e777f 100644 --- a/kernel/events/uprobes.c +++ b/kernel/events/uprobes.c @@ -1201,8 +1201,8 @@ int uprobe_register_refctr(struct inode *inode, loff_t offset, EXPORT_SYMBOL_GPL(uprobe_register_refctr); /* - * uprobe_apply - unregister an already registered probe. - * @inode: the file in which the probe has to be removed. + * uprobe_apply - register a probe or unregister an already registered probe. + * @inode: the file in which the probe has to be placed or removed. * @offset: offset from the start of the file. * @uc: consumer which wants to add more or remove some breakpoints * @add: add or remove the breakpoints -- 2.34.1
