From: Ben Hutchings <bhutchings@solarflare.com>
To: <jiang.biao2@zte.com.cn>
Cc: Sony Chacko <sony.chacko@qlogic.com>,
Rajesh Borundia <rajesh.borundia@qlogic.com>,
<netdev@vger.kernel.org>, <li.fengmao@zte.com.cn>
Subject: Re: [Patch] netxen_nic: Bugfix for wrong RUNNING status of NX3031 NICs with no link
Date: Thu, 2 Jan 2014 14:47:13 +0000 [thread overview]
Message-ID: <1388674033.1607.3.camel@bwh-desktop.uk.level5networks.com> (raw)
In-Reply-To: <OFAE440C7C.FE33E30C-ON48257C54.0013C383-48257C54.0013F43B@zte.com.cn>
On Thu, 2014-01-02 at 11:37 +0800, jiang.biao2@zte.com.cn wrote:
> From: Li Fengmao <li.fengmao@zte.com.cn>
>
> Ifconfig command displays RUNNING status when there is no link on
> NX3031 NICs. The problem is caused by the wrong calling order of
> netif_carrier_off() and register_netdev() in netxen_setup_netdev(),
> dev->reg_state is initialized to NETREG_UNINITIALIZED before
> registering network device, so the linkwatch_fire_event() will not
> be called to notify the link change event in netif_carrier_off(),
> and the operational status of network device will be set to
> IF_OPER_UNKNOWN. In that case, the IFF_RUNNING flags will be set,
> which result in the wrong RUNNING status in the result of ifconfig
> command.
[...]
This was fixed in Linux 3.7. The driver should not be changed.
(This change may be worthwhile in an out-of-tree version for older
kernel versions, but beware of races with opening of the device.)
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2014-01-02 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 3:37 [Patch] netxen_nic: Bugfix for wrong RUNNING status of NX3031 NICs with no link jiang.biao2
2014-01-02 14:47 ` Ben Hutchings [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-02 6:32 jiang.biao2
2014-01-02 8:24 ` David Miller
2014-01-02 9:16 ` jiang.biao2
2014-01-02 18:00 ` Ben Hutchings
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=1388674033.1607.3.camel@bwh-desktop.uk.level5networks.com \
--to=bhutchings@solarflare.com \
--cc=jiang.biao2@zte.com.cn \
--cc=li.fengmao@zte.com.cn \
--cc=netdev@vger.kernel.org \
--cc=rajesh.borundia@qlogic.com \
--cc=sony.chacko@qlogic.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