Displaying 4 results from an estimated 4 matches for "c2bc66082e10".
2019 Oct 16
4
read_barrier_depends() usage in vhost.c
...supposed need for a compiler barrier
either (read_barrier_depends() doesn't generally provide this).
Does anybody know which accesses are being ordered here? Usually you'd need
a READ_ONCE()/rcu_dereference() beginning the chain, but I haven't managed
to find one...
Thanks,
Will
[1] c2bc66082e10 ("locking/barriers: Add implicit smp_read_barrier_depends() to READ_ONCE()")
2019 Oct 16
4
read_barrier_depends() usage in vhost.c
...supposed need for a compiler barrier
either (read_barrier_depends() doesn't generally provide this).
Does anybody know which accesses are being ordered here? Usually you'd need
a READ_ONCE()/rcu_dereference() beginning the chain, but I haven't managed
to find one...
Thanks,
Will
[1] c2bc66082e10 ("locking/barriers: Add implicit smp_read_barrier_depends() to READ_ONCE()")
2019 Oct 17
0
read_barrier_depends() usage in vhost.c
...rasnlate_desc() that stores the userspace buffer pointer in the iov
2) copy_from_iter() that reads from those pointers
So we need a data dependency barrier in the middle as explained in the
memory-barriers.txt? (since READ_ONCE is not used in iov iterator).
Thanks
>
> Will
>
> [1] c2bc66082e10 ("locking/barriers: Add implicit smp_read_barrier_depends() to READ_ONCE()")
2019 Oct 16
0
read_barrier_depends() usage in vhost.c
...barrier_depends() doesn't generally provide this).
>
> Does anybody know which accesses are being ordered here? Usually you'd need
> a READ_ONCE()/rcu_dereference() beginning the chain, but I haven't managed
> to find one...
>
> Thanks,
>
> Will
>
> [1] c2bc66082e10 ("locking/barriers: Add implicit smp_read_barrier_depends() to READ_ONCE()")