From: Sean Anderson <sean.anderson@seco.com>
To: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org
Cc: Madalin Bucur <madalin.bucur@nxp.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: fman: Unregister ethernet device on removal
Date: Thu, 3 Nov 2022 15:07:10 -0400 [thread overview]
Message-ID: <00d3b2e3-6c93-0e48-e87b-ebd9c6574e00@seco.com> (raw)
In-Reply-To: <20221103182831.2248833-1-sean.anderson@seco.com>
On 11/3/22 14:28, Sean Anderson wrote:
> When the mac device gets removed, it leaves behind the ethernet device.
> This will result in a segfault next time the ethernet device accesses
> mac_dev. Remove the ethernet device when we get removed to prevent
> this. This is not completely reversible, since some resources aren't
> cleaned up properly, but that can be addressed later.
>
> Fixes: 3933961682a3 ("fsl/fman: Add FMan MAC driver")
> Signed-off-by: Sean Anderson <sean.anderson@seco.com>
> ---
> So... why *do* we have a separate device for the ethernet interface?
> Can't the mac device just register the netdev itself?
>
> drivers/net/ethernet/freescale/fman/mac.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/net/ethernet/freescale/fman/mac.c b/drivers/net/ethernet/freescale/fman/mac.c
> index 65df308bad97..13e67f2864be 100644
> --- a/drivers/net/ethernet/freescale/fman/mac.c
> +++ b/drivers/net/ethernet/freescale/fman/mac.c
> @@ -487,12 +487,21 @@ static int mac_probe(struct platform_device *_of_dev)
> return err;
> }
>
> +static int mac_remove(struct platform_device *pdev)
> +{
> + struct mac_device *mac_dev = platform_get_drvdata(pdev);
> +
> + platform_device_unregister(mac_dev->priv->eth_dev);
> + return 0;
> +}
> +
> static struct platform_driver mac_driver = {
> .driver = {
> .name = KBUILD_MODNAME,
> .of_match_table = mac_match,
> },
> .probe = mac_probe,
> + .remove = mac_remove,
> };
>
> builtin_platform_driver(mac_driver);
err, this should be [PATCH net]. Sorry, will fix if necessary for a v2.
--Sena
next prev parent reply other threads:[~2022-11-03 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 18:28 Sean Anderson
2022-11-03 19:07 ` Sean Anderson [this message]
2022-11-05 3:00 ` patchwork-bot+netdevbpf
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=00d3b2e3-6c93-0e48-e87b-ebd9c6574e00@seco.com \
--to=sean.anderson@seco.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madalin.bucur@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®