linux-kernel - Re: [git pull] sparseirq / irq updates for v2.6.29

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: <2f11576a0812270927taef068fobbad997dc5e5aacf@mail.gmail.com>
Date:	Sun, 28 Dec 2008 02:27:43 +0900
From:	"KOSAKI Motohiro" <kosaki.motohiro@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	"Jesse Barnes" <jbarnes@...tuousgeek.org>
Subject: Re: [git pull] sparseirq / irq updates for v2.6.29

> ------------------>
> Ingo Molnar (2):
>      sparseirq: do not printk when migrating IRQ descriptors
>      sparseirq: fix desc->lock init
>
> KOSAKI Motohiro (4):
>      hrtimer: remove #include <linux/irq.h>
>      irq: for_each_irq_desc() move to irqnr.h
>      proc: remove ifdef CONFIG_SPARSE_IRQ from stat.c
>      irq: simplify for_each_irq_desc() usage
>
> Yinghai Lu (4):
>      sparseirq: remove duplicated arch_early_irq_init()
>      sparseirq: work around compiler optimizing away __weak functions

Unfortunately, this workaround doesn't workaround.
Kamalesh reported kernel still crashes.

So, I suggest to pending this pull request awhile.
Nobody want to merge pseudo fix.



>      sparseirq: fix hang with !SPARSE_IRQ
>      sparseirq: set lock_class for legacy irq when sparse_irq is selected
--
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/