From: Ioana Ciornei <ioana.ciornei@nxp.com>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH net] net: dpaa2-switch: disable the control interface on error path
Date: Thu, 19 Aug 2021 15:29:49 +0000 [thread overview]
Message-ID: <20210819152947.cnx3vyueud6rfupn@skbuf> (raw)
In-Reply-To: <20210819141755.1931423-1-vladimir.oltean@nxp.com>
On Thu, Aug 19, 2021 at 05:17:55PM +0300, Vladimir Oltean wrote:
> Currently dpaa2_switch_takedown has a funny name and does not do the
> opposite of dpaa2_switch_init, which makes probing fail when we need to
> handle an -EPROBE_DEFER.
>
> A sketch of what dpaa2_switch_init does:
>
> dpsw_open
>
> dpaa2_switch_detect_features
>
> dpsw_reset
>
> for (i = 0; i < ethsw->sw_attr.num_ifs; i++) {
> dpsw_if_disable
>
> dpsw_if_set_stp
>
> dpsw_vlan_remove_if_untagged
>
> dpsw_if_set_tci
>
> dpsw_vlan_remove_if
> }
>
> dpsw_vlan_remove
>
> alloc_ordered_workqueue
>
> dpsw_fdb_remove
>
> dpaa2_switch_ctrl_if_setup
>
> When dpaa2_switch_takedown is called from the error path of
> dpaa2_switch_probe(), the control interface, enabled by
> dpaa2_switch_ctrl_if_setup from dpaa2_switch_init, remains enabled,
> because dpaa2_switch_takedown does not call
> dpaa2_switch_ctrl_if_teardown.
>
> Since dpaa2_switch_probe might fail due to EPROBE_DEFER of a PHY, this
> means that a second probe of the driver will happen with the control
> interface directly enabled.
>
> This will trigger a second error:
>
> [ 93.273528] fsl_dpaa2_switch dpsw.0: dpsw_ctrl_if_set_pools() failed
> [ 93.281966] fsl_dpaa2_switch dpsw.0: fsl_mc_driver_probe failed: -13
> [ 93.288323] fsl_dpaa2_switch: probe of dpsw.0 failed with error -13
>
> Which if we investigate the /dev/dpaa2_mc_console log, we find out is
> caused by:
>
> [E, ctrl_if_set_pools:2211, DPMNG] ctrl_if must be disabled
>
> So make dpaa2_switch_takedown do the opposite of dpaa2_switch_init (in
> reasonable limits, no reason to change STP state, re-add VLANs etc), and
> rename it to something more conventional, like dpaa2_switch_teardown.
>
> Fixes: 613c0a5810b7 ("staging: dpaa2-switch: enable the control interface")
> Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Ioana Ciornei <ioana.ciornei@nxp.com>
Thanks!
next prev parent reply other threads:[~2021-08-19 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 14:17 [PATCH net] net: dpaa2-switch: disable the control interface on error path Vladimir Oltean
2021-08-19 15:29 ` Ioana Ciornei [this message]
2021-08-19 18:15 ` Jakub Kicinski
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=20210819152947.cnx3vyueud6rfupn@skbuf \
--to=ioana.ciornei@nxp.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vladimir.oltean@nxp.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