summaryrefslogtreecommitdiff
path: root/scripts/generate_rust_analyzer.py
diff options
context:
space:
mode:
authorJiri Olsa <jolsa@kernel.org>2024-09-24 14:07:30 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-02-21 16:01:46 +0300
commitd5c8ffaa9d532974d5e48d4ac267be5e7b1d9d5d (patch)
tree898dca23667302c6c1ba4b7b1d341bb243547fa4 /scripts/generate_rust_analyzer.py
parent449dd20852d8563d5e9c32a9228a106d8399570a (diff)
downloadlinux-d5c8ffaa9d532974d5e48d4ac267be5e7b1d9d5d.tar.xz
selftests/bpf: Fix uprobe consumer test
commit 4b7c05598a644782b8451e415bb56f31e5c9d3ee upstream. With newly merged code the uprobe behaviour is slightly different and affects uprobe consumer test. We no longer need to check if the uprobe object is still preserved after removing last uretprobe, because it stays as long as there's pending/installed uretprobe instance. This allows to run uretprobe consumers registered 'after' uprobe was hit even if previous uretprobe got unregistered before being hit. The uprobe object will be now removed after the last uprobe ref is released and in such case it's held by ri->uprobe (return instance) which is released after the uretprobe is hit. Reported-by: Ihor Solodrai <ihor.solodrai@pm.me> Signed-off-by: Jiri Olsa <jolsa@kernel.org> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Tested-by: Ihor Solodrai <ihor.solodrai@pm.me> Closes: https://lore.kernel.org/bpf/w6U8Z9fdhjnkSp2UaFaV1fGqJXvfLEtDKEUyGDkwmoruDJ_AgF_c0FFhrkeKW18OqiP-05s9yDKiT6X-Ns-avN_ABf0dcUkXqbSJN1TQSXo=@pm.me/ Signed-off-by: Alexei Starovoitov <ast@kernel.org> Cc: Alan Maguire <alan.maguire@oracle.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions