Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1282697 > unrolled thread
| Started by | David Miller <davem@davemloft.net> |
|---|---|
| First post | 2015-12-03 05:40 +0100 |
| Last post | 2015-12-03 06:40 +0100 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH net] ipv6: add complete rcu protection around np->opt David Miller <davem@davemloft.net> - 2015-12-03 05:40 +0100
Re: [PATCH net] ipv6: add complete rcu protection around np->opt Eric Dumazet <eric.dumazet@gmail.com> - 2015-12-03 06:40 +0100
| From | David Miller <davem@davemloft.net> |
|---|---|
| Date | 2015-12-03 05:40 +0100 |
| Subject | Re: [PATCH net] ipv6: add complete rcu protection around np->opt |
| Message-ID | <qBtQu-6V-7@gated-at.bofh.it> |
From: Eric Dumazet <eric.dumazet@gmail.com> Date: Sun, 29 Nov 2015 19:37:57 -0800 > From: Eric Dumazet <edumazet@google.com> > > This patch addresses multiple problems : > > UDP/RAW sendmsg() need to get a stable struct ipv6_txoptions > while socket is not locked : Other threads can change np->opt > concurrently. Dmitry posted a syzkaller > (http://github.com/google/syzkaller) program desmonstrating > use-after-free. > > Starting with TCP/DCCP lockless listeners, tcp_v6_syn_recv_sock() > and dccp_v6_request_recv_sock() also need to use RCU protection > to dereference np->opt once (before calling ipv6_dup_options()) > > This patch adds full RCU protection to np->opt > > Reported-by: Dmitry Vyukov <dvyukov@google.com> > Signed-off-by: Eric Dumazet <edumazet@google.com> Applied and queued up for -stable. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [next] | [standalone]
| From | Eric Dumazet <eric.dumazet@gmail.com> |
|---|---|
| Date | 2015-12-03 06:40 +0100 |
| Message-ID | <qBuMx-JD-1@gated-at.bofh.it> |
| In reply to | #1282697 |
On Wed, 2015-12-02 at 23:38 -0500, David Miller wrote: > From: Eric Dumazet <eric.dumazet@gmail.com> > Date: Sun, 29 Nov 2015 19:37:57 -0800 > > > From: Eric Dumazet <edumazet@google.com> > > > > This patch addresses multiple problems : > > > > UDP/RAW sendmsg() need to get a stable struct ipv6_txoptions > > while socket is not locked : Other threads can change np->opt > > concurrently. Dmitry posted a syzkaller > > (http://github.com/google/syzkaller) program desmonstrating > > use-after-free. > > > > Starting with TCP/DCCP lockless listeners, tcp_v6_syn_recv_sock() > > and dccp_v6_request_recv_sock() also need to use RCU protection > > to dereference np->opt once (before calling ipv6_dup_options()) > > > > This patch adds full RCU protection to np->opt > > > > Reported-by: Dmitry Vyukov <dvyukov@google.com> > > Signed-off-by: Eric Dumazet <edumazet@google.com> > > Applied and queued up for -stable. Thanks David. I will send a followup patch, as I missed the sctp part, now triggering following sparse warnings. CHECK net/sctp/ipv6.c net/sctp/ipv6.c:223:41: warning: incorrect type in argument 4 (different address spaces) net/sctp/ipv6.c:223:41: expected struct ipv6_txoptions *opt net/sctp/ipv6.c:223:41: got struct ipv6_txoptions [noderef] <asn:4>*opt net/sctp/ipv6.c:265:41: warning: incorrect type in argument 2 (different address spaces) net/sctp/ipv6.c:265:41: expected struct ipv6_txoptions const *opt net/sctp/ipv6.c:265:41: got struct ipv6_txoptions [noderef] <asn:4>*opt net/sctp/ipv6.c:324:49: warning: incorrect type in argument 2 (different address spaces) net/sctp/ipv6.c:324:49: expected struct ipv6_txoptions const *opt net/sctp/ipv6.c:324:49: got struct ipv6_txoptions [noderef] <asn:4>*opt -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web