doc: event notifier on kretprobe is not supported
authorFrancis Deslauriers <francis.deslauriers@efficios.com>
Tue, 21 Jan 2020 20:57:16 +0000 (15:57 -0500)
committerMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Wed, 18 Nov 2020 18:15:01 +0000 (13:15 -0500)
The kretprobe behavior is to fire twice (entry and exit of target
function), placing an event notifier on such function does not make
sense at first glance. If we come up with a use case it will be quite
easy to enable.

Signed-off-by: Francis Deslauriers <francis.deslauriers@efficios.com>
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Change-Id: I6f214501706d1ef170c81b80a1f82c039d687502

src/lttng-abi.c

index 7001aa0e9237e0729512855a295ae42ff9a16b93..1407d41bd218de7685fceaa677770f189fb3e437 100644 (file)
@@ -1811,8 +1811,9 @@ int lttng_abi_create_event_notifier(struct file *event_notifier_group_file,
        case LTTNG_KERNEL_KPROBE:
                event_notifier_param->event.u.kprobe.symbol_name[LTTNG_KERNEL_SYM_NAME_LEN - 1] = '\0';
                break;
-       case LTTNG_KERNEL_UPROBE:
        case LTTNG_KERNEL_KRETPROBE:
+               /* Placing a trigger on kretprobe is not supported. */
+       case LTTNG_KERNEL_UPROBE:
        case LTTNG_KERNEL_FUNCTION:
        case LTTNG_KERNEL_NOOP:
        case LTTNG_KERNEL_SYSCALL:
This page took 0.026836 seconds and 4 git commands to generate.