netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Wang <sean.wang@mediatek.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: <netdev@vger.kernel.org>, <andrew@lunn.ch>,
	<vivien.didelot@savoirfairelinux.com>, <davem@davemloft.net>,
	<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH net] net: dsa: Initialize ds->cpu_port_mask earlier
Date: Wed, 26 Jul 2017 10:13:28 +0800	[thread overview]
Message-ID: <1501035208.27236.2.camel@mtkswgap22> (raw)
In-Reply-To: <20170724174923.29156-1-f.fainelli@gmail.com>

Hi, Florian

the solution is better and also can fix the problem I originally
reported. Thank for your immediate help :-)

Sean


On Mon, 2017-07-24 at 10:49 -0700, Florian Fainelli wrote:
> The mt7530 driver has its dsa_switch_ops::get_tag_protocol function
> check ds->cpu_port_mask to issue a warning in case the configured CPU
> port is not capable of supporting tags.
> 
> After commit 14be36c2c96c ("net: dsa: Initialize all CPU and enabled
> ports masks in dsa_ds_parse()") we slightly re-arranged the
> initialization such that this was no longer working. Just make sure that
> ds->cpu_port_mask is set prior to the first call to get_tag_protocol,
> thus restoring the expected contract. In case of error, the CPU port bit
> is cleared.
> 
> Fixes: 14be36c2c96c ("net: dsa: Initialize all CPU and enabled ports masks in dsa_ds_parse()")
> Reported-by: Sean Wang <sean.wang@mediatek.com>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
> Sean, can you check this does fix the problem you originally reported
> correctly for you? Thanks!
> 
>  net/dsa/dsa2.c | 13 +++++++------
>  1 file changed, 7 insertions(+), 6 deletions(-)
> 
> diff --git a/net/dsa/dsa2.c b/net/dsa/dsa2.c
> index 56e46090526b..c442051d5a55 100644
> --- a/net/dsa/dsa2.c
> +++ b/net/dsa/dsa2.c
> @@ -509,21 +509,22 @@ static int dsa_cpu_parse(struct dsa_port *port, u32 index,
>  		dst->cpu_dp->netdev = ethernet_dev;
>  	}
>  
> +	/* Initialize cpu_port_mask now for drv->setup()
> +	 * to have access to a correct value, just like what
> +	 * net/dsa/dsa.c::dsa_switch_setup_one does.
> +	 */
> +	ds->cpu_port_mask |= BIT(index);
> +
>  	tag_protocol = ds->ops->get_tag_protocol(ds);
>  	dst->tag_ops = dsa_resolve_tag_protocol(tag_protocol);
>  	if (IS_ERR(dst->tag_ops)) {
>  		dev_warn(ds->dev, "No tagger for this switch\n");
> +		ds->cpu_port_mask &= ~BIT(index);
>  		return PTR_ERR(dst->tag_ops);
>  	}
>  
>  	dst->rcv = dst->tag_ops->rcv;
>  
> -	/* Initialize cpu_port_mask now for drv->setup()
> -	 * to have access to a correct value, just like what
> -	 * net/dsa/dsa.c::dsa_switch_setup_one does.
> -	 */
> -	ds->cpu_port_mask |= BIT(index);
> -
>  	return 0;
>  }
>  

      parent reply	other threads:[~2017-07-26  2:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 17:49 [PATCH net] net: dsa: Initialize ds->cpu_port_mask earlier Florian Fainelli
2017-07-25  0:36 ` David Miller
2017-07-26  2:13 ` Sean Wang [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=1501035208.27236.2.camel@mtkswgap22 \
    --to=sean.wang@mediatek.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=linux-mediatek@lists.infradead.org \
    --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).