From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Cong Wang <xiyou.wangcong@gmail.com>,
Anoob Soman <anoob.soman@citrix.com>,
Dmitry Vyukov <dvyukov@google.com>,
David Miller <davem@davemloft.net>,
Willem de Bruijn <willemb@google.com>,
Eric Dumazet <edumazet@google.com>,
Daniel Borkmann <daniel@iogearbox.net>,
jarno@ovn.org, philip.pettersson@gmail.com,
weongyo.linux@gmail.com, netdev <netdev@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: net/packet: use-after-free in packet_rcv_fanout
Date: Sun, 12 Feb 2017 20:42:39 -0500 [thread overview]
Message-ID: <20170213014239.GA21934@oracle.com> (raw)
In-Reply-To: <1486749763.7793.152.camel@edumazet-glaptop3.roam.corp.google.com>
On (02/10/17 10:02), Eric Dumazet wrote:
> At least, Anoob patch is making a step into the right direction ;)
> https://patchwork.ozlabs.org/patch/726532/
I've not been able to reproduce Dmitry's panic (though I did not try
very hard either) but there's a call to fanout_release from packet_release
before the synchronize_net() - I wonder if this could end up kfree'ing f
when there are threads in the middle of dev_queue_xmit_nit().
--Sowmini
next prev parent reply other threads:[~2017-02-13 1:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 13:14 net/packet: use-after-free in packet_rcv_fanout Dmitry Vyukov
2017-02-09 15:12 ` Sowmini Varadhan
2017-02-09 15:17 ` Eric Dumazet
2017-02-10 1:24 ` Cong Wang
2017-02-10 3:19 ` Eric Dumazet
2017-02-10 3:23 ` Eric Dumazet
2017-02-10 17:49 ` Cong Wang
2017-02-10 17:59 ` Eric Dumazet
2017-02-10 18:02 ` Cong Wang
2017-02-10 18:15 ` Eric Dumazet
2017-02-10 18:02 ` Eric Dumazet
2017-02-10 18:34 ` Cong Wang
2017-02-13 1:42 ` Sowmini Varadhan [this message]
2017-02-13 15:17 ` Dmitry Vyukov
2017-02-17 19:27 ` Cong Wang
2017-02-10 3:33 ` Sowmini Varadhan
2017-02-10 4:18 ` Eric Dumazet
2017-02-10 18:00 ` Cong Wang
2017-02-10 19:16 ` Sowmini Varadhan
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=20170213014239.GA21934@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=anoob.soman@citrix.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=jarno@ovn.org \
--cc=netdev@vger.kernel.org \
--cc=philip.pettersson@gmail.com \
--cc=syzkaller@googlegroups.com \
--cc=weongyo.linux@gmail.com \
--cc=willemb@google.com \
--cc=xiyou.wangcong@gmail.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 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.