From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: tom.parkin@gmail.com, netdev@vger.kernel.org
Subject: Re: BUG: NULL pointer dereference in netif_carrier_off
Date: Thu, 10 Jan 2013 14:37:37 -0800 (PST) [thread overview]
Message-ID: <20130110.143737.1586417148052592077.davem@davemloft.net> (raw)
In-Reply-To: <1357842765.27446.2396.camel@edumazet-glaptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, 10 Jan 2013 10:32:45 -0800
> [PATCH net-next] veth: fix a NULL deref in netif_carrier_off
>
> In commit d0e2c55e7c94 (veth: avoid a NULL deref in veth_stats_one)
> we now clear the peer pointers in veth_dellink()
>
> veth_close() must therefore make sure the peer pointer is set.
>
> Reported-by: Tom Parkin <tom.parkin@gmail.com>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
Applied.
prev parent reply other threads:[~2013-01-10 22:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 17:50 BUG: NULL pointer dereference in netif_carrier_off Tom Parkin
2013-01-10 17:56 ` Eric Dumazet
2013-01-10 18:32 ` Eric Dumazet
2013-01-10 22:37 ` David Miller [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=20130110.143737.1586417148052592077.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tom.parkin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).