From: Florian Fainelli <f.fainelli@gmail.com>
To: Fugang Duan <b38611@freescale.com>, davem@davemloft.net
Cc: netdev@vger.kernel.org, bhutchings@solarflare.com
Subject: Re: [PATCH net-next 1/1] net: fec: add netif status check before set mac address
Date: Tue, 8 Sep 2015 20:37:51 -0700 [thread overview]
Message-ID: <55EFA98F.7010700@gmail.com> (raw)
In-Reply-To: <1441766567-30689-1-git-send-email-b38611@freescale.com>
Le 09/08/15 19:42, Fugang Duan a écrit :
> There exist one issue by below case that case system hang:
> ifconfig eth0 down
> ifconfig eth0 hw ether 00:10:19:19:81:19
>
> After eth0 down, all fec clocks are gated off. In the .fec_set_mac_address()
> function, it will set new MAC address to registers, which causes system hang.
>
> So it needs to add netif status check to avoid registers access when clocks are
> gated off. Until eth0 up the new MAC address are wrote into related registers.
Since this is a bug fix, do not you intend to target the "net" tree
instead of "net-next"?
>
> Signed-off-by: Fugang Duan <B38611@freescale.com>
> ---
> drivers/net/ethernet/freescale/fec_main.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/net/ethernet/freescale/fec_main.c b/drivers/net/ethernet/freescale/fec_main.c
> index 91925e3..cd09dbb 100644
> --- a/drivers/net/ethernet/freescale/fec_main.c
> +++ b/drivers/net/ethernet/freescale/fec_main.c
> @@ -3029,6 +3029,9 @@ fec_set_mac_address(struct net_device *ndev, void *p)
> memcpy(ndev->dev_addr, addr->sa_data, ndev->addr_len);
> }
>
> + if (!netif_running(ndev))
> + return 0;
> +
> writel(ndev->dev_addr[3] | (ndev->dev_addr[2] << 8) |
> (ndev->dev_addr[1] << 16) | (ndev->dev_addr[0] << 24),
> fep->hwp + FEC_ADDR_LOW);
>
--
Florian
next prev parent reply other threads:[~2015-09-09 3:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 2:42 [PATCH net-next 1/1] net: fec: add netif status check before set mac address Fugang Duan
2015-09-09 3:37 ` Florian Fainelli [this message]
2015-09-09 3:45 ` Duan Andy
2015-09-09 21:13 ` David Miller
2015-09-09 9:14 ` Lucas Stach
2015-09-10 1:05 ` Duan Andy
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=55EFA98F.7010700@gmail.com \
--to=f.fainelli@gmail.com \
--cc=b38611@freescale.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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).