netdev - Re: [PATCH] e1000 stop raw interrupts disabled nag from RT

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]

Date:	Thu, 01 Mar 2007 08:55:34 -0800
From:	"Kok, Auke" <auke-jan.h.kok@...el.com>
To:	Mark Huth <mhuth@...sta.com>
CC:	"Kok, Auke" <auke-jan.h.kok@...el.com>, netdev@...r.kernel.org,
	Jesse Brandeburg <jesse.brandeburg@...el.com>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH] e1000 stop raw interrupts disabled nag from RT

Mark Huth wrote:
> Kok, Auke wrote:
>> Mark Huth wrote:
>>> Current e1000_xmit_frame spews raw interrupt disabled nag messages when
>>> used with RT kernel patches.  This patch uses spin_trylock_irqsave,
>>> which allows RT patches to properly manage the irq semantics.
>> Looks OK with me on first sight, I'll keep it on my stack and push it 
>> upstream after Jesse looks it over.
>>
>> Which -RT paches make this pop up btw? I'd like to repro it.
>>
> 
> Well, I'm not an expert on the realtime patches - but most any patch set 
> from Ingo seems to set this off - we've run through a bunch all the way 
> since 2.6.10.

that's bizarre, and would imply that Ingo himself never spotted this in ages, 
not to mention never tell us about it?

Ingo?
-
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