From: Andrew Lunn <andrew@lunn.ch>
To: Mattias Forsblad <mattias.forsblad@gmail.com>
Cc: netdev@vger.kernel.org, Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [RFC net-next PATCH 1/3] dsa: Add ability to handle RMU frames.
Date: Thu, 18 Aug 2022 14:44:06 +0200 [thread overview]
Message-ID: <Yv40FjX9WTx8aBih@lunn.ch> (raw)
In-Reply-To: <20220818102924.287719-2-mattias.forsblad@gmail.com>
> +static int dsa_inband_rcv_ll(struct sk_buff *skb, struct net_device *dev)
> +{
> + int source_device, source_port;
> + struct dsa_switch *ds;
> + u8 *dsa_header;
> + int rcv_seqno;
> + int ret = 0;
> +
> + if (!dev || !dev->dsa_ptr)
> + return 0;
> +
> + ds = dev->dsa_ptr->ds;
> +
> + dsa_header = skb->data - 2;
> +
> + source_device = dsa_header[0] & 0x1f;
> + source_port = (dsa_header[1] >> 3) & 0x1f;
> + ds = dsa_switch_find(ds->dst->index, source_device);
You should never trust anything you receive from the network. Always
validate it. ds could be a NULL pointer here, if source_device is
bad. source_port could also be invalid. Hum, source port is not
actually used?
We send RMU frames with a specific destination MAC address. Can we
validate the destination address for frames we receive.
> +
> + /* Get rcv seqno */
> + rcv_seqno = dsa_header[3];
> +
> + skb_pull(skb, DSA_HLEN);
> +
> + if (ds->ops && ds->ops->inband_receive(ds, skb, rcv_seqno))
> + netdev_err(dev, "DSA inband: error decoding packet");
rate limit this print, so as to avoid the possibility of a DoS.
Andrew
next prev parent reply other threads:[~2022-08-18 12:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 10:29 [RFC net-next PATCH 0/3] net: dsa: mv88e6xxx: Add RMU support Mattias Forsblad
2022-08-18 10:29 ` [RFC net-next PATCH 1/3] dsa: Add ability to handle RMU frames Mattias Forsblad
2022-08-18 12:44 ` Andrew Lunn [this message]
2022-08-19 5:21 ` Mattias Forsblad
2022-08-18 10:29 ` [RFC net-next PATCH 2/3] mv88e6xxx: Implement remote management support (RMU) Mattias Forsblad
2022-08-18 13:21 ` Andrew Lunn
2022-08-19 5:28 ` Mattias Forsblad
2022-08-19 12:29 ` Andrew Lunn
2022-08-18 10:29 ` [RFC net-next PATCH 3/3] mv88e6xxx: rmon: Use RMU to collect rmon data Mattias Forsblad
2022-08-18 15:36 ` Andrew Lunn
2022-08-19 5:47 ` Mattias Forsblad
2022-08-18 11:58 ` [RFC net-next PATCH 0/3] net: dsa: mv88e6xxx: Add RMU support Vladimir Oltean
2022-08-19 5:07 ` Mattias Forsblad
2022-08-18 12:31 ` Andrew Lunn
2022-08-19 5:14 ` Mattias Forsblad
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=Yv40FjX9WTx8aBih@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=mattias.forsblad@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=vivien.didelot@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).