Lines Matching refs:value

104 fed into some operation that checks the full value against a later marked
105 load from memory, which means that the occasional arbitrarily bogus value
106 is not a problem.  For example, if a bogus value is fed into cmpxchg(),
108 in a retry.  Unless the race condition that resulted in the bogus value
113 architectures.  Therefore, it is best to capture the return value from
116 Capturing the return value from cmpxchg() also saves a memory reference
151 After all, if the heuristic can tolerate the occasional bogus value
153 compiler-mangled write, at least assuming that the proper value is in
195 	b.	When the store writes the value already contained in
275 		pr_info("Current value of foo: %d\n", data_race(foo));
286 read_foo_diagnostic() might sometimes return a bogus value.
293 		pr_info("Current value of foo: %d\n", data_race(READ_ONCE(foo)));
301 		pr_info("Current value of foo: %d\n", READ_ONCE(foo));
307 the value of foo, you also need CONFIG_KCSAN_REPORT_VALUE_CHANGE_ONLY=n.
418 If the value read from global_flag is true, then global_flag is
423 Otherwise, if either value read from global_flag is true, then after