diff options
author | Willem de Bruijn <willemb@google.com> | 2020-07-01 16:00:06 -0400 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2020-07-01 17:38:30 -0700 |
commit | 0da7536fb47f51df89ccfcb1fa09f249d9accec5 (patch) | |
tree | c82adb4f2c69ea1284d6c450bbae33e833f1620f /init | |
parent | e114e1e8ac9d31f25b9dd873bab5d80c1fc482ca (diff) | |
download | linux-0da7536fb47f51df89ccfcb1fa09f249d9accec5.tar.gz linux-0da7536fb47f51df89ccfcb1fa09f249d9accec5.tar.bz2 linux-0da7536fb47f51df89ccfcb1fa09f249d9accec5.zip |
ip: Fix SO_MARK in RST, ACK and ICMP packets
When no full socket is available, skbs are sent over a per-netns
control socket. Its sk_mark is temporarily adjusted to match that
of the real (request or timewait) socket or to reflect an incoming
skb, so that the outgoing skb inherits this in __ip_make_skb.
Introduction of the socket cookie mark field broke this. Now the
skb is set through the cookie and cork:
<caller> # init sockc.mark from sk_mark or cmsg
ip_append_data
ip_setup_cork # convert sockc.mark to cork mark
ip_push_pending_frames
ip_finish_skb
__ip_make_skb # set skb->mark to cork mark
But I missed these special control sockets. Update all callers of
__ip(6)_make_skb that were originally missed.
For IPv6, the same two icmp(v6) paths are affected. The third
case is not, as commit 92e55f412cff ("tcp: don't annotate
mark on control socket from tcp_v6_send_response()") replaced
the ctl_sk->sk_mark with passing the mark field directly as a
function argument. That commit predates the commit that
introduced the bug.
Fixes: c6af0c227a22 ("ip: support SO_MARK cmsg")
Signed-off-by: Willem de Bruijn <willemb@google.com>
Reported-by: Martin KaFai Lau <kafai@fb.com>
Reviewed-by: Martin KaFai Lau <kafai@fb.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions