From: linas@austin.ibm.com (Linas Vepstas)
To: Arnd Bergmann <arnd@arndb.de>
Cc: cbe-oss-dev@ozlabs.org, netdev@vger.kernel.org,
Christian Krafft <krafft@de.ibm.com>
Subject: Re: [PATCH] spidernet: enable poll() before registering interrupts
Date: Mon, 20 Aug 2007 17:29:45 -0500 [thread overview]
Message-ID: <20070820222945.GJ4261@austin.ibm.com> (raw)
In-Reply-To: <200707120119.12589.arnd@arndb.de>
On Thu, Jul 12, 2007 at 01:19:11AM +0200, Arnd Bergmann wrote:
> We must not call netif_poll_enable after enabling interrupts,
> because an interrupt might come in and set the __LINK_STATE_RX_SCHED
> bit before we get to clear that bit again. If that happens,
> the next call to the ->poll() function will oops.
>
> Signed-off-by: Arnd Bergmann <arnd.bergmann@de.ibm.com>
> ---
> This was found during testing with the fedora kernel,
> with all patches from netdev-2.6.git applied.
>
> It may not be the right fix, but this is currently the
> only way I can get that kernel to boot.
>
> One part I don't understand at the moment is that Christian
> Krafft reported the same problem with tg3, but that driver
> has all interrupts disabled at the device while calling
> the request_irq() function, which seems to be the best
> solution for avoiding the bug in the first place.
It apears that this patch does not apply cleanly any more,
and I think that's a good thing!
An intervening patch changed the init so that the
hardware interrupts aren't enabled until after the
request_irq, and after the poll_enable(). Thus,
it seems this pach is no longer needed, right?
I'll pursue with Kou Ishizaki, who pointed out that
I'd missed your email.
--linas
next prev parent reply other threads:[~2007-08-20 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 23:19 [PATCH] spidernet: enable poll() before registering interrupts Arnd Bergmann
2007-08-20 22:20 ` Linas Vepstas
2007-08-20 22:29 ` Linas Vepstas [this message]
2007-08-20 23:06 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2007-08-22 0:27 Ishizaki Kou
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=20070820222945.GJ4261@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=arnd@arndb.de \
--cc=cbe-oss-dev@ozlabs.org \
--cc=krafft@de.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.