Searched refs:ASSERT_EXCLUSIVE_WRITER (Results 1 – 7 of 7) sorted by relevance
255 ASSERT_EXCLUSIVE_WRITER(hist->count[i]); in bp_slots_histogram_max()273 ASSERT_EXCLUSIVE_WRITER(hist1->count[i]); in bp_slots_histogram_max_merge()274 ASSERT_EXCLUSIVE_WRITER(hist2->count[i]); in bp_slots_histogram_max_merge()
370 #define ASSERT_EXCLUSIVE_WRITER(var) \ macro
223 ASSERT_EXCLUSIVE_WRITER(foo) tells KCSAN that although it is OK for there229 ASSERT_EXCLUSIVE_ACCESS() or ASSERT_EXCLUSIVE_WRITER() on the one hand332 ASSERT_EXCLUSIVE_WRITER(foo);344 of the ASSERT_EXCLUSIVE_WRITER() is to allow KCSAN to check for a buggy465 not make sense to use ASSERT_EXCLUSIVE_WRITER() in this case because
1458 ASSERT_EXCLUSIVE_WRITER(rcu_state.gp_seq); in rcu_gp_init()1790 ASSERT_EXCLUSIVE_WRITER(rcu_state.gp_seq); in rcu_gp_cleanup()4534 ASSERT_EXCLUSIVE_WRITER(rcu_state.ncpus); in rcu_cpu_starting()
506 ASSERT_EXCLUSIVE_WRITER(orig->vm_flags); in vm_area_dup()507 ASSERT_EXCLUSIVE_WRITER(orig->vm_file); in vm_area_dup()
229 :functions: ASSERT_EXCLUSIVE_WRITER ASSERT_EXCLUSIVE_WRITER_SCOPED
363 ASSERT_EXCLUSIVE_WRITER(test_var); in test_kernel_assert_writer()