Function report

Linux Kernel

v5.5.9

Brick Technologies Co., Ltd

Source Code:kernel\events\uprobes.c Create Date:2022-07-28 13:45:03
Last Modify:2020-03-12 14:18:49 Copyright©Brick
home page Tree
Annotation kernel can get tool activityDownload SCCTChinese

Name:put_uprobe

Proto:static void put_uprobe(struct uprobe *uprobe)

Type:void

Parameter:

TypeParameterName
struct uprobe *uprobe
609  If _dec_and_test - decrement a refcount and test if it is 0*@r: the refcount* Similar to atomic_dec_and_test(), it will WARN on underflow and fail to* decrement when saturated at REFCOUNT_SATURATED Then
615  mutex_lock( & delayed_uprobe_lock)
616  delayed_uprobe_remove(uprobe, NULL)
617  mutex_unlock - release the mutex*@lock: the mutex to be released* Unlock a mutex that has been locked by this task previously.* This function must not be used in interrupt context. Unlocking* of a not locked mutex is not allowed.
618  kfree(uprobe)
Caller
NameDescribe
alloc_uprobe
delete_uprobeThere could be threads that have already hit the breakpoint. They* will recheck the current insn and restart if find_uprobe() fails.* See find_active_uprobe().
uprobe_unregisterprobe_unregister - unregister an already registered probe.*@inode: the file in which the probe has to be removed.*@offset: offset from the start of the file.*@uc: identify which probe if multiple probes are colocated.
__uprobe_register__uprobe_register - register a probe*@inode: the file in which the probe has to be placed
uprobe_applyprobe_apply - unregister an already registered probe.*@inode: the file in which the probe has to be 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
uprobe_mmapCalled from mmap_region/vma_adjust with mm->mmap_sem acquired.* Currently we ignore all errors and always return 0, the callers* can't handle the failure anyway.
free_ret_instance
uprobe_free_utaskCalled with no locks held.* Called in context of an exiting or an exec-ing thread.
handle_swbpRun handler and ask thread to singlestep.* Ensure all non-fatal signals cannot interrupt thread while it singlesteps.
handle_singlestepPerform required fix-ups and disable singlestep.* Allow pending signals to take effect.