From: Eric Dumazet <eric.dumazet@gmail.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Eric Dumazet <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, John Stultz <johnstul@us.ibm.com>,
Paul Moore <paul@paul-moore.com>,
Eric Paris <eparis@parisplace.org>,
"Serge E. Hallyn" <serge@hallyn.com>
Subject: Re: NULL pointer dereference BUG in ip_send_skb()
Date: Fri, 10 Aug 2012 18:45:46 +0200 [thread overview]
Message-ID: <1344617146.31104.2736.camel@edumazet-glaptop> (raw)
In-Reply-To: <20120810163112.GA32544@localhost>
On Sat, 2012-08-11 at 00:31 +0800, Fengguang Wu wrote:
> Hi Eric,
>
> This line triggers a NULL deference since commit 3a7c384 ("ipv4: tcp:
> unicast_sock should not land outside of TCP stack").
>
> int ip_send_skb(struct sk_buff *skb)
> {
> ==> struct net *net = sock_net(skb->sk);
Hi Fengguang
Fix was sent some hours ago, on netdev list.
http://patchwork.ozlabs.org/patch/176483/
Thanks
prev parent reply other threads:[~2012-08-10 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 16:31 NULL pointer dereference BUG in ip_send_skb() Fengguang Wu
2012-08-10 16:45 ` Eric Dumazet [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=1344617146.31104.2736.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eparis@parisplace.org \
--cc=fengguang.wu@intel.com \
--cc=johnstul@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.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