linux-kernel - Re: 044d408409cc4e1bc75c886e27ca85c270db104c causes warnings

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] [day] [month] [year] [list]

Date:	Fri, 1 May 2009 15:25:01 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Russell King <rmk+lkml@....linux.org.uk>
cc:	Linux Kernel List <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: 044d408409cc4e1bc75c886e27ca85c270db104c causes warnings

On Fri, 1 May 2009, Russell King wrote:

> People have been complaining about this new warning which has appeared,
> but unfortunately none of them seem to have reported this to the relevent
> people.  I've just had someone else mention about this, so I guess I'm
> going to have to do the legwork for them...
> 
> Adding the WARN_ONCE() in 044d408409cc4e1bc75c886e27ca85c270db104c
> causes warnings to appear on ARM.  Eg,
> 
> WARNING: at /build/linux/kernel/irq/handle.c:353 handle_IRQ_event+0x58/0xd8()
> BUG: IRQ handler called from non-hardirq context!
> Backtrace:
> [<c0460e60>] (handle_IRQ_event+0x0/0xd8) from [<c046257c>] (handle_edge_irq+0x114/0x150)
> [<c0462468>] (handle_edge_irq+0x0/0x150) from [<c0461b80>] (resend_irqs+0x48/0x80)
> [<c0461b38>] (resend_irqs+0x0/0x80) from [<c043ffa8>] (tasklet_action+0x88/0xe0)
> [<c043ff20>] (tasklet_action+0x0/0xe0) from [<c043f9e0>] (__do_softirq+0x68/0x104)
> 
> to which tglx said:
> 
> --- Day changed Mon Mar 30 2009
> 17:03 < tglx> rmk: hmpf
> 17:44 < rmk> tglx: seems to be nicely reproducable when accessing stuff via a PCMCIA NE2K NIC on PXA
> 17:44 < tglx> sure
> 17:44 < tglx> I know why it triggers
> 17:45 < tglx> darn
> 17:53 < tglx> the warn_once is crap when you use the resend mechanism, which runs in a tasklet :(
> 
> So the question is: what's happening about this?

Queued a revert for linus.

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/