netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mugunthan V N <mugunthanvnm@ti.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: <netdev@vger.kernel.org>, <tglx@linutronix.de>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 3/5 v2] net/cpsw: don't rely only on netif_running() to check which device is active
Date: Mon, 22 Apr 2013 14:44:59 +0530	[thread overview]
Message-ID: <5174FF93.8070408@ti.com> (raw)
In-Reply-To: <20130422083048.GA8162@linutronix.de>

On 4/22/2013 2:00 PM, Sebastian Andrzej Siewior wrote:
> I tried to describe the reason for that in my patch description. Here
> it is again: netif_running() reports false before ndo_close() has been
> called. That means an interrupt between the flag change and interrupt
> disabling in ndo_close() will currently lockup the box (IRQ_NONE would
> at least allow the core to disable the interrupt line).
>
> Initialyly I decided against using IFF_UP as well but using would work
> without the private active field. So here we have
>
> -v1…v2: replacing private active field with IFF_UP + netif_running()
>
> How about this?
If this is the case, then other Ethernet drivers will also have the same 
scenario,
if it can be fixed in a generic way then i will be good.

Regards
Mugunthan V N

  reply	other threads:[~2013-04-22  9:16 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17 21:52 my small cpsw queue Sebastian Andrzej Siewior
2013-04-17 21:52 ` [PATCH 1/5] net/davinci_cpdma: don't check for jiffies with interrupts Sebastian Andrzej Siewior
2013-04-18 11:49   ` Mugunthan V N
2013-04-17 21:52 ` [PATCH 2/5] net/cpsw: don't continue if we miss to allocate rx skbs Sebastian Andrzej Siewior
2013-04-18 11:50   ` Mugunthan V N
2013-04-18 12:09     ` Sebastian Andrzej Siewior
2013-04-19 10:40       ` Mugunthan V N
2013-04-22  8:05         ` Sebastian Andrzej Siewior
2013-04-17 21:52 ` [PATCH 3/5] net/cpsw: don't rely on netif_running() to check which device is active Sebastian Andrzej Siewior
2013-04-18 11:50   ` Mugunthan V N
2013-04-18 12:10     ` Sebastian Andrzej Siewior
2013-04-19 10:35       ` Mugunthan V N
2013-04-22  8:30         ` [PATCH 3/5 v2] net/cpsw: don't rely only " Sebastian Andrzej Siewior
2013-04-22  9:14           ` Mugunthan V N [this message]
2013-04-22  9:30             ` Sebastian Andrzej Siewior
2013-04-22  9:40               ` Mugunthan V N
2013-04-22  9:49                 ` Sebastian Andrzej Siewior
2013-04-22 10:12                   ` Mugunthan V N
2013-04-22 10:19                     ` Sebastian Andrzej Siewior
2013-04-22 19:21           ` David Miller
2013-04-19 13:10   ` [PATCH 3/5] net/cpsw: don't rely " Sergei Shtylyov
2013-04-22  8:33     ` Sebastian Andrzej Siewior
2013-04-17 21:52 ` [PATCH 4/5] net/davinci_cpdma: remove unused argument in cpdma_chan_submit() Sebastian Andrzej Siewior
2013-04-18 11:51   ` Mugunthan V N
2013-04-17 21:52 ` [PATCH 5/5] net/cpsw: redo rx skb allocation in rx path Sebastian Andrzej Siewior
2013-04-18 11:50   ` Mugunthan V N
2013-04-18 12:13     ` Sebastian Andrzej Siewior
2013-04-19 10:28       ` Mugunthan V N
2013-04-18 14:59     ` Eric Dumazet

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=5174FF93.8070408@ti.com \
    --to=mugunthanvnm@ti.com \
    --cc=bigeasy@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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).