# Re: KASAN: use-after-free Read in task\_is\_descendant

- From: Oleg Nesterov \<oleg@redhat.com\>
- Date: 2018-10-25 16:26:00 
- List: linux-security-module
- Page: https://ratatoskr.run/linux-security-module/2018/10/5416510
- Thread: https://ratatoskr.run/linux-security-module/2018/10/5413381/t.md

```text
On 10/25, Oleg Nesterov wrote:
>
> Because our rcu read-lock critical section extends beyond the return from
> synchronize_rcu(), and thus we must have a full memory barrier _between_
> that synchronize_rcu() and our rcu_read_lock(). We must see all memory updates,
> including thread_pid = NULL which makes pid_alive() == F.

In case I was not clear....

Suppose we have int X = 0. If some CPU does

	X = 1;
	synchronize_rcu();

and another CPU does

	rcu_read_lock();
	x = X;
	rcu_read_unlock();

then x should be == 1 in case when rcu_read_unlock() happens _after_ return
from synchronize_rcu().

Oleg.

```
