From: Sasha Levin <sasha.levin@oracle.com>
To: "Oleg A. Arkhangelsky" <sysoleg@yandex.ru>, "xeb@mail.ru" <xeb@mail.ru>
Cc: "David S. Miller" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>
Subject: Re: net: pptp: bad RCU usage and use after free
Date: Sun, 06 Apr 2014 10:01:57 -0400 [thread overview]
Message-ID: <53415E55.4080307@oracle.com> (raw)
In-Reply-To: <1868621396767667@web26m.yandex.ru>
On 04/06/2014 03:01 AM, Oleg A. Arkhangelsky wrote:
>
>
> 05.04.2014, 19:53, "Sasha Levin" <sasha.levin@oracle.com>:
>
>> My guess is that we're racing the synchronize_rcu() in del_chan() with
>> the RCU protected read in lookup_chan_dst():
>>
>> pptp_release()
>> del_chan() lookup_chan_dst()
>> enter synchronize_rcu()
>> sock = rcu_dereference(...)
>> exit synchronize_rcu()
>> release_sock()
>> sock_put()
>> opt = &sock->proto.pptp;
>> [ boom ]
>
> Hmm...
>
> IMHO, sock from callid_sock array must be NULL (not uninitialized) at
> that point, because del_chan() do:
>
> RCU_INIT_POINTER(callid_sock[sock->proto.pptp.src_addr.call_id], NULL);
>
> before rcu_synchronize(). I think that prevents access to freeing item
> in subsequent readers that go inside critical section when
> rcu_synchronize() is active.
Right, make sense. I'm completely lost then.
Thanks,
Sasha
prev parent reply other threads:[~2014-04-06 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-05 15:52 net: pptp: bad RCU usage and use after free Sasha Levin
[not found] ` <1868621396767667@web26m.yandex.ru>
2014-04-06 14:01 ` Sasha Levin [this message]
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=53415E55.4080307@oracle.com \
--to=sasha.levin@oracle.com \
--cc=davej@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sysoleg@yandex.ru \
--cc=xeb@mail.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.