mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <edumazet@google.com>
Cc: <davem@davemloft.net>, <dsahern@kernel.org>, <kuba@kernel.org>,
	<kuni1840@gmail.com>, <kuniyu@amazon.com>,
	<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
	<pabeni@redhat.com>, <syzkaller-bugs@googlegroups.com>
Subject: Re: [PATCH v1 net 5/5] tcp: Fix data races around icsk->icsk_af_ops.
Date: Tue, 27 Sep 2022 09:48:24 -0700	[thread overview]
Message-ID: <20220927164824.36027-1-kuniyu@amazon.com> (raw)
In-Reply-To: <CANn89iLyqG8SRmHhWZOZUc-HDR88z_TNZn4_zbJz5MW4+kh2ZQ@mail.gmail.com>

From:   Eric Dumazet <edumazet@google.com>
Date:   Tue, 27 Sep 2022 09:39:37 -0700
> On Tue, Sep 27, 2022 at 9:33 AM Kuniyuki Iwashima <kuniyu@amazon.com> wrote:
> >
> > IPV6_ADDRFORM changes icsk->icsk_af_ops under lock_sock(), but
> > tcp_(get|set)sockopt() read it locklessly.  To avoid load/store
> > tearing, we need to add READ_ONCE() and WRITE_ONCE() for the reads
> > and write.
> 
> I am pretty sure I have released a syzkaller bug recently with this issue.
> Have you seen this?
> If yes, please include the appropriate syzbot tag.

No, I haven't.
Could you provide the URL?
I'm happy to include the syzbot tag and KCSAN report in the changelog.


> > Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> > Signed-off-by: Kuniyuki Iwashima <kuniyu@amazon.com>
> > ---
> >  net/ipv4/tcp.c           | 10 ++++++----
> >  net/ipv6/ipv6_sockglue.c |  3 ++-
> >  2 files changed, 8 insertions(+), 5 deletions(-)
> >
> > diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c
> > index e373dde1f46f..c86dd0ccef5b 100644
> > --- a/net/ipv4/tcp.c
> > +++ b/net/ipv4/tcp.c
> > @@ -3795,8 +3795,9 @@ int tcp_setsockopt(struct sock *sk, int level, int optname, sockptr_t optval,
> >         const struct inet_connection_sock *icsk = inet_csk(sk);
> >
> >         if (level != SOL_TCP)
> > -               return icsk->icsk_af_ops->setsockopt(sk, level, optname,
> > -                                                    optval, optlen);
> > +               /* IPV6_ADDRFORM can change icsk->icsk_af_ops under us. */
> > +               return READ_ONCE(icsk->icsk_af_ops)->setsockopt(sk, level, optname,
> > +                                                               optval, optlen);
> >         return do_tcp_setsockopt(sk, level, optname, optval, optlen);
> >  }
> >  EXPORT_SYMBOL(tcp_setsockopt);
> > @@ -4394,8 +4395,9 @@ int tcp_getsockopt(struct sock *sk, int level, int optname, char __user *optval,
> >         struct inet_connection_sock *icsk = inet_csk(sk);
> >
> >         if (level != SOL_TCP)
> > -               return icsk->icsk_af_ops->getsockopt(sk, level, optname,
> > -                                                    optval, optlen);
> > +               /* IPV6_ADDRFORM can change icsk->icsk_af_ops under us. */
> > +               return READ_ONCE(icsk->icsk_af_ops)->getsockopt(sk, level, optname,
> > +                                                               optval, optlen);
> >         return do_tcp_getsockopt(sk, level, optname, optval, optlen);
> >  }
> >  EXPORT_SYMBOL(tcp_getsockopt);
> > diff --git a/net/ipv6/ipv6_sockglue.c b/net/ipv6/ipv6_sockglue.c
> > index a89db5872dc3..726d95859898 100644
> > --- a/net/ipv6/ipv6_sockglue.c
> > +++ b/net/ipv6/ipv6_sockglue.c
> > @@ -479,7 +479,8 @@ static int do_ipv6_setsockopt(struct sock *sk, int level, int optname,
> >
> >                                 /* Paired with READ_ONCE(sk->sk_prot) in inet6_stream_ops */
> >                                 WRITE_ONCE(sk->sk_prot, &tcp_prot);
> > -                               icsk->icsk_af_ops = &ipv4_specific;
> > +                               /* Paired with READ_ONCE() in tcp_(get|set)sockopt() */
> > +                               WRITE_ONCE(icsk->icsk_af_ops, &ipv4_specific);
> >                                 sk->sk_socket->ops = &inet_stream_ops;
> >                                 sk->sk_family = PF_INET;
> >                                 tcp_sync_mss(sk, icsk->icsk_pmtu_cookie);
> > --
> > 2.30.2
> >

  reply	other threads:[~2022-09-27 16:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 16:12 [PATCH v1 net 0/5] tcp/udp: Fix memory leaks and data races around IPV6_ADDRFORM Kuniyuki Iwashima
2022-09-27 16:12 ` [PATCH v1 net 1/5] tcp/udp: Fix memory leak in ipv6_renew_options() Kuniyuki Iwashima
2022-09-27 16:12 ` [PATCH v1 net 2/5] udp: Call inet6_destroy_sock() in setsockopt(IPV6_ADDRFORM) Kuniyuki Iwashima
2022-09-27 16:12 ` [PATCH v1 net 3/5] tcp/udp: Call inet6_destroy_sock() in IPv4 sk_prot->destroy() Kuniyuki Iwashima
2022-09-27 16:50   ` Eric Dumazet
2022-09-27 17:02     ` Kuniyuki Iwashima
2022-09-27 16:12 ` [PATCH v1 net 4/5] ipv6: Fix data races around sk->sk_prot Kuniyuki Iwashima
2022-09-27 16:12 ` [PATCH v1 net 5/5] tcp: Fix data races around icsk->icsk_af_ops Kuniyuki Iwashima
2022-09-27 16:39   ` Eric Dumazet
2022-09-27 16:48     ` Kuniyuki Iwashima [this message]
2022-09-27 16:53       ` Kuniyuki Iwashima
2022-09-27 17:56         ` Eric Dumazet
2022-09-27 16:55       ` Eric Dumazet
2022-09-27 17:07         ` Kuniyuki Iwashima

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220927164824.36027-1-kuniyu@amazon.com \
    --to=kuniyu@amazon.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=kuni1840@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®