Searched refs:death (Results 1 – 11 of 11) sorted by relevance
1220 if (ref->death) { in binder_cleanup_ref_olocked()1360 kfree(ref->death); in binder_free_ref()4325 death = kzalloc(sizeof(*death), GFP_KERNEL); in binder_thread_write()4350 kfree(death); in binder_thread_write()4377 ref->death = death; in binder_thread_write()4395 death = ref->death; in binder_thread_write()4456 death); in binder_thread_write()4890 kfree(death); in binder_thread_read()5152 kfree(death); in binder_release_work()6145 int death = 0; in binder_node_release() local[all …]
337 struct binder_ref_death *death; member
720 static void cps_shutdown_this_cpu(enum cpu_death death) in cps_shutdown_this_cpu() argument727 if (death == CPU_DEATH_HALT) { in cps_shutdown_this_cpu()
810 goto death; in tcp_keepalive_timer()859 death: in tcp_keepalive_timer()
37 has died; such a mutex is said to be abandoned. Owner death is not38 tracked automatically based on thread death, but rather must be
1868 이 코드는 객체의 업데이트된 death 마크가 레퍼런스 카운터 감소 동작
709 This actually supposed to ensure death of the CPU. Actually look at some
12 a SIGBUS and often dies an unhappy death. Shortly after huge page support
1908 This makes sure that the death mark on the object is perceived to be set
1134 relaxed cat would be considered to cycle between death and life more
1402 D: parent process death signal to children