netdev - Re: REGRESSION: panic on e1000 driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070531050616.GA32391@gondor.apana.org.au>
Date:	Thu, 31 May 2007 15:06:16 +1000
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	"Kok, Auke" <auke-jan.h.kok@...el.com>
Cc:	Doug Chapman <doug.chapman@...com>, netdev@...r.kernel.org,
	e1000-devel@...ts.sourceforge.net
Subject: Re: REGRESSION: panic on e1000 driver

On Wed, May 30, 2007 at 09:51:14PM -0700, Kok, Auke wrote:
> 
> this has been an age-old confusion that I never grasped either, so I 
> perfectly understand why you added the explicit e1000_disable_irq call in 
> the other patch (and think thats a great idea). But really, there should be 
> a way for a driver to tell the stack that it should really keep it's hands 
> off :)

Well yes, you can get the stack to keep away by not registering your
device :)

> BTW e1000 currently triggers a single irq manually in the watchdog as link 
> goes up, so that might be the one that is giving problems now. In any case 
> I can't reproduce any of it - perhaps my hardware is too fast. Time to whip 
> out the pIII :o

Hmm, if it's triggered by the watchdog then that means the watchdog has
been scheduled.  However, it seems that the only way to schedule it is
through an interrupt?

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html