diff options
author | Eric Dumazet <edumazet@google.com> | 2015-11-30 05:03:11 +0100 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2015-12-01 21:45:05 +0100 |
commit | ceb5d58b217098a657f3850b7a2640f995032e62 (patch) | |
tree | 4d12375d4193b130ec15daac9acea099b7083544 /security | |
parent | net: rename SOCK_ASYNC_NOSPACE and SOCK_ASYNC_WAITDATA (diff) | |
download | linux-ceb5d58b217098a657f3850b7a2640f995032e62.tar.xz linux-ceb5d58b217098a657f3850b7a2640f995032e62.zip |
net: fix sock_wake_async() rcu protection
Dmitry provided a syzkaller (http://github.com/google/syzkaller)
triggering a fault in sock_wake_async() when async IO is requested.
Said program stressed af_unix sockets, but the issue is generic
and should be addressed in core networking stack.
The problem is that by the time sock_wake_async() is called,
we should not access the @flags field of 'struct socket',
as the inode containing this socket might be freed without
further notice, and without RCU grace period.
We already maintain an RCU protected structure, "struct socket_wq"
so moving SOCKWQ_ASYNC_NOSPACE & SOCKWQ_ASYNC_WAITDATA into it
is the safe route.
It also reduces number of cache lines needing dirtying, so might
provide a performance improvement anyway.
In followup patches, we might move remaining flags (SOCK_NOSPACE,
SOCK_PASSCRED, SOCK_PASSSEC) to save 8 bytes and let 'struct socket'
being mostly read and let it being shared between cpus.
Reported-by: Dmitry Vyukov <dvyukov@google.com>
Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions