linux-kernel - Re: [PATCH] irqchip: brcmstb-l2: Level-2 interrupts are edge sensitive

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:	Sat, 21 Jun 2014 00:09:55 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Florian Fainelli <f.fainelli@...il.com>
cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Jason Cooper <jason@...edaemon.net>
Subject: Re: [PATCH] irqchip: brcmstb-l2: Level-2 interrupts are edge
 sensitive

On Fri, 20 Jun 2014, Florian Fainelli wrote:
> 2014-06-12 12:13 GMT-07:00 Florian Fainelli <f.fainelli@...il.com>:
> > 2014-06-09 11:05 GMT-07:00 Florian Fainelli <f.fainelli@...il.com>:
> >> The driver was configuring the interrupt handler for the Level-2
> >> interrupts to be "level" triggered while they are in fact "edge"
> >> triggered. Fix this by using the correct handler.
> >>
> >> Reported-by: Brian Norris <computersforpeace@...il.com>
> >> Signed-off-by: Florian Fainelli <f.fainelli@...il.com>
> >
> > Jason, Thomas, this driver just got merged into 3.16-rc0, can you
> > carry this fix such that it gets into a future 3.16-rc? Thanks!
> 
> Ping! I want to make sure this gets into a next 3.16-rc pull request.
> Andrew, can you take that one if neither Thomas nor Andrew respond in
> a timely manner?

So Andrew should take it if neither Thomas nor Andrew respond. I'm
curious how that works out.

Dude, keep calm. Timely manner?

For something you brought yourself into the merge window and does not
bring the world to a grinding halt like a nasty NULL pointer
dereference in the scheduler?

I have no problem with a polite reminder as stuff falls down the
cracks occassionaly, but please keep the proportions right. The only
user of the code YOU wreckaged has a bugfix already, so what's the
problem whether this hits rc2 or rc3?

Thanks,

	tglx

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/