From: Laszlo Toth <laszlth@gmail.com>
To: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Cc: Laszlo Toth <laszlth@gmail.com>,
Stephen Hemminger <stephen@networkplumber.org>,
"David S. Miller" <davem@davemloft.net>,
bridge@lists.linux-foundation.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net: bridge: add missing NULL checks
Date: Tue, 10 Apr 2018 19:22:43 +0200 [thread overview]
Message-ID: <20180410172243.GA4230@laszlth> (raw)
In-Reply-To: <3db78abd-bc13-528f-9da3-cb9a0ce0f617@cumulusnetworks.com>
On Mon, Apr 09, 2018 at 01:25:41AM +0300, Nikolay Aleksandrov wrote:
> On 08/04/18 20:49, Laszlo Toth wrote:
> >br_port_get_rtnl() can return NULL
> >
> >Signed-off-by: Laszlo Toth <laszlth@gmail.com>
> >---
> > net/bridge/br_netlink.c | 12 ++++++++++--
> > 1 file changed, 10 insertions(+), 2 deletions(-)
> >
>
> Nacked-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
> More below.
>
> >diff --git a/net/bridge/br_netlink.c b/net/bridge/br_netlink.c
> >index 015f465c..cbec11f 100644
> >--- a/net/bridge/br_netlink.c
> >+++ b/net/bridge/br_netlink.c
> >@@ -939,14 +939,17 @@ static int br_port_slave_changelink(struct net_device *brdev,
> > struct nlattr *data[],
> > struct netlink_ext_ack *extack)
> > {
> >+ struct net_bridge_port *port = br_port_get_rtnl(dev);
> > struct net_bridge *br = netdev_priv(brdev);
> > int ret;
> > if (!data)
> > return 0;
> >+ if (!port)
> >+ return -EINVAL;
>
> If we're here, it means the master device of dev is a bridge => dev is a bridge port,
> since we're running with RTNL that cannot change, so this check is unnecessary.
>
> Have you actually hit a bug with this code ?
>
> > spin_lock_bh(&br->lock);
> >- ret = br_setport(br_port_get_rtnl(dev), data);
> >+ ret = br_setport(port, data);
> > spin_unlock_bh(&br->lock);
> > return ret;
> >@@ -956,7 +959,12 @@ static int br_port_fill_slave_info(struct sk_buff *skb,
> > const struct net_device *brdev,
> > const struct net_device *dev)
> > {
> >- return br_port_fill_attrs(skb, br_port_get_rtnl(dev));
> >+ struct net_bridge_port *port = br_port_get_rtnl(dev);
> >+
> >+ if (!port)
> >+ return -EINVAL;
> >+
> >+ return br_port_fill_attrs(skb, port);
>
> Same rationale here, fill_slave_info is called via a master device's ops
> under RTNL, which means dev is a bridge port and that also cannot change.
>
> If you have hit a bug with this code, can we see the trace ?
> The problem might be elsewhere.
There was a NULL dereference in br_port_fill_attrs(), but on a much
older release w/ a probably buggy and custom driver,
so there is no real problem to trace.
Anyway I thought I'd make a quick patch from it, but you're right,
it's pointless to validate twice.
Please just ignore the patch.
Laszlo
>
> Thanks,
> Nik
>
> > }
> > static size_t br_port_get_slave_size(const struct net_device *brdev,
> >
>
prev parent reply other threads:[~2018-04-10 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 17:49 [PATCH] net: bridge: add missing NULL checks Laszlo Toth
2018-04-08 22:25 ` Nikolay Aleksandrov
2018-04-10 17:22 ` Laszlo Toth [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=20180410172243.GA4230@laszlth \
--to=laszlth@gmail.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=stephen@networkplumber.org \
/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).