From: David Miller <davem@davemloft.net>
To: socketcan@hartkopp.net
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH stable 3.7+] fib_frontend: fix possible NULL pointer dereference
Date: Fri, 24 Jan 2014 15:52:06 -0800 (PST) [thread overview]
Message-ID: <20140124.155206.1783075688524593121.davem@davemloft.net> (raw)
In-Reply-To: <52E0DEA6.3060803@hartkopp.net>
From: Oliver Hartkopp <socketcan@hartkopp.net>
Date: Thu, 23 Jan 2014 10:19:34 +0100
> The two commits 0115e8e30d (net: remove delay at device dismantle) and
> 748e2d9396a (net: reinstate rtnl in call_netdevice_notifiers()) silently
> removed a NULL pointer check for in_dev since Linux 3.7.
>
> This patch re-introduces this check as it causes crashing the kernel when
> setting small mtu values on non-ip capable netdevices.
>
> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
Applied and queued up for -stable, thanks.
prev parent reply other threads:[~2014-01-24 23:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 9:19 [PATCH stable 3.7+] fib_frontend: fix possible NULL pointer dereference Oliver Hartkopp
2014-01-23 12:26 ` Eric Dumazet
2014-01-24 23:52 ` 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=20140124.155206.1783075688524593121.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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