From: "Li, Zhen-Hua" <zhen-hual@hp.com>
To: Sathya Perla <Sathya.Perla@Emulex.Com>
Cc: Subramanian Seetharaman <subbu.seetharaman@Emulex.Com>,
Ajit Khaparde <Ajit.Khaparde@Emulex.Com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] driver/net: add missing rtnl lock/unlock for benet
Date: Tue, 15 Apr 2014 12:59:56 +0000 [thread overview]
Message-ID: <1249C41B-D72F-40C8-A8F1-D135D02A1511@hp.com> (raw)
In-Reply-To: <069bdb52-6176-407a-b7fc-3f23a944a529@CMEXHTCAS2.ad.emulex.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb2312", Size: 1004 bytes --]
Yes, that's ok for me.
·¢×ÔÎÒµÄ iPhone
ÔÚ 2014Äê4ÔÂ15ÈÕ£¬ÏÂÎç7:57£¬"Sathya Perla" <Sathya.Perla@Emulex.Com> дµÀ£º
>> -----Original Message-----
>> From: Li, ZhenHua [mailto:zhen-hual@hp.com]
>>
>> Because netif_running() is called in netif_device_detach and
>> netif_device_attach. To avoid dev status changed while
>> netif_device_detach/attach is not finished, I think a rtnl_lock and
>> unlock should be called to avoid this.
>
> Ok. I'd like to then factor the code slightly differently by using
> routines like this:
>
> be_close_sync() {
> rtnl_lock();
>
> netif_device_detach(netdev);
> if (netif_running(netdev))
> be_close(netdev);
>
> rtnl_unlock();
> }
>
> and similarly for be_open_sync()
>
> And, I'd need some time to test these flows too.
> Would you be OK with this?
>
> thanks,
> -Sathya
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2014-04-15 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 6:45 Li, Zhen-Hua
2014-04-15 8:07 ` Sathya Perla
2014-04-15 9:02 ` Li, ZhenHua
2014-04-15 11:57 ` Sathya Perla
2014-04-15 12:59 ` Li, Zhen-Hua [this message]
2014-04-15 19:09 ` David Miller
2014-04-16 6:30 ` Li, ZhenHua
2014-04-16 7:09 ` Li, ZhenHua
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=1249C41B-D72F-40C8-A8F1-D135D02A1511@hp.com \
--to=zhen-hual@hp.com \
--cc=Ajit.Khaparde@Emulex.Com \
--cc=Sathya.Perla@Emulex.Com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=subbu.seetharaman@Emulex.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®