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: [PATCH net-next v4 3/6] net: dsa: Introduce dsa tagger data operation.
Date: Tue, 6 Sep 2022 15:08:23 +0200 [thread overview]
Message-ID: <YxdGR/TPuNf7E0w1@lunn.ch> (raw)
In-Reply-To: <20220906063450.3698671-4-mattias.forsblad@gmail.com>
> switch (code) {
> case DSA_CODE_FRAME2REG:
> - /* Remote management is not implemented yet,
> - * drop.
> - */
> + tagger_data = ds->tagger_data;
> + if (likely(tagger_data->decode_frame2reg))
> + tagger_data->decode_frame2reg(dev, skb);
> return NULL;
> case DSA_CODE_ARP_MIRROR:
> case DSA_CODE_POLICY_MIRROR:
> @@ -323,6 +326,25 @@ static struct sk_buff *dsa_rcv_ll(struct sk_buff *skb, struct net_device *dev,
> return skb;
> }
> +static void dsa_tag_disconnect(struct dsa_switch *ds)
> +{
> + kfree(ds->tagger_data);
> + ds->tagger_data = NULL;
> +}
Probably a question for Vladimir.
Is there a potential use after free here? Is it guaranteed that the
masters dev->dsa_ptr will be cleared before the disconnect function is
called?
Also, the receive function checks for tagger_data->decode_frame2reg,
but does not check for tagger_data != NULL.
This is just a straight copy of tag_qca, so if there are issues here,
they are probably not new issues.
Andrew
next prev parent reply other threads:[~2022-09-06 13:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 6:34 [PATCH net-next v4 0/6] net: dsa: mv88e6xxx: qca8k: rmon: Add RMU support Mattias Forsblad
2022-09-06 6:34 ` [PATCH net-next v4 1/6] net: dsa: mv88e6xxx: Add RMU enable for select switches Mattias Forsblad
2022-09-06 12:29 ` Andrew Lunn
2022-09-07 5:55 ` Mattias Forsblad
2022-09-06 21:46 ` Florian Fainelli
2022-09-07 6:29 ` Mattias Forsblad
2022-09-06 6:34 ` [PATCH net-next v4 2/6] net: dsa: Add convenience functions for frame handling Mattias Forsblad
2022-09-06 12:43 ` Andrew Lunn
2022-09-07 6:19 ` Mattias Forsblad
2022-09-06 21:44 ` Florian Fainelli
2022-09-08 11:32 ` Paolo Abeni
2022-09-06 6:34 ` [PATCH net-next v4 3/6] net: dsa: Introduce dsa tagger data operation Mattias Forsblad
2022-09-06 13:08 ` Andrew Lunn [this message]
2022-09-06 13:51 ` Vladimir Oltean
2022-09-06 6:34 ` [PATCH net-next v4 4/6] net: dsa: mv88e6xxxx: Add RMU functionality Mattias Forsblad
2022-09-06 6:34 ` [PATCH net-next v4 5/6] net: dsa: mv88e6xxx: rmon: Use RMU for reading RMON data Mattias Forsblad
2022-09-06 6:34 ` [PATCH net-next v4 6/6] net: dsa: qca8k: Use new convenience functions Mattias Forsblad
2022-09-06 8:07 ` [PATCH net-next v4 0/6] net: dsa: mv88e6xxx: qca8k: rmon: Add RMU support Marek Behún
2022-09-06 9:45 ` 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=YxdGR/TPuNf7E0w1@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).