From: Florian Fainelli <f.fainelli@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
vivien.didelot@savoirfairelinux.com
Subject: Re: [PATCH net-next v2] net: dsa: Mock-up driver
Date: Fri, 31 Mar 2017 09:40:37 -0700 [thread overview]
Message-ID: <3952b60b-1c24-487d-7f8d-9cad5dc69dcc@gmail.com> (raw)
In-Reply-To: <20170331160601.GC12814@lunn.ch>
Hi Andrew,
On 03/31/2017 09:06 AM, Andrew Lunn wrote:
> Hi Florian
>
>> +static enum dsa_tag_protocol dsa_loop_get_protocol(struct dsa_switch *ds)
>> +{
>> + dev_dbg(ds->dev, "%s\n", __func__);
>> +
>> + return DSA_TAG_PROTO_NONE;
>> +}
>
> I'm wondering how safe this is:
>
> static const struct dsa_device_ops none_ops = {
> .xmit = dsa_slave_notag_xmit,
> .rcv = NULL,
> };
>
> /*
> * If the CPU connects to this switch, set the switch tree
> * tagging protocol to the preferred tagging format of this
> * switch.
> */
> if (dst->cpu_switch == ds) {
> enum dsa_tag_protocol tag_protocol;
>
> tag_protocol = ops->get_tag_protocol(ds);
> dst->tag_ops = dsa_resolve_tag_protocol(tag_protocol);
> if (IS_ERR(dst->tag_ops))
> return PTR_ERR(dst->tag_ops);
>
> dst->rcv = dst->tag_ops->rcv;
> }
>
>
> static int dsa_switch_rcv(struct sk_buff *skb, struct net_device *dev,
> struct packet_type *pt, struct net_device *orig_dev)
> {
> struct dsa_switch_tree *dst = dev->dsa_ptr;
>
> if (unlikely(dst == NULL)) {
> kfree_skb(skb);
> return 0;
> }
>
> return dst->rcv(skb, dev, pt, orig_dev);
> }
>
> static struct packet_type dsa_pack_type __read_mostly = {
> .type = cpu_to_be16(ETH_P_XDSA),
> .func = dsa_switch_rcv,
> };
>
> It looks like when a frame is received, we are going to dereference a
> NULL pointer.
Actually we do not, because netdev_uses_dsa() returns true only when
dst->rcv is different from NULL. When dst->rcv is NULL we completely
bypass the DSA hook in eth_type_trans() and everything is well, the
master network device is the one receiving packets.
This is actually the intended behavior for netdev_uses_dsa() because it
really tells whether there is a DSA tagging protocol set-up and that is
what NIC drivers (e.g: bcmsysport) would care about.
Thanks!
--
Florian
next prev parent reply other threads:[~2017-03-31 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 1:43 [PATCH net-next v2] net: dsa: Mock-up driver Florian Fainelli
2017-03-31 16:06 ` Andrew Lunn
2017-03-31 16:40 ` Florian Fainelli [this message]
2017-03-31 16:56 ` Andrew Lunn
2017-04-01 19:40 ` David Miller
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=3952b60b-1c24-487d-7f8d-9cad5dc69dcc@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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).