The patch titled
start_kernel: test if irq's got enabled early, barf, and disable them again
has been removed from the -mm tree. Its filename was
start_kernel-test-if-irqs-got-enabled-early-barf-and-disable-them-again.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: start_kernel: test if irq's got enabled early, barf, and disable them
again
From: Ard van Breemen <[EMAIL PROTECTED]>
The calls made by parse_parms to other initialization code might enable
interrupts again way too early.
Having interrupts on this early can make systems PANIC when they initialize
the IRQ controllers (which happens later in the code). This patch detects
that irq's are enabled again, barfs about it and disables them again as a
safety net.
[EMAIL PROTECTED]: cleanups]
Signed-off-by: Ard van Breemen <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---
init/main.c | 5 +++++
1 file changed, 5 insertions(+)
diff -puN
init/main.c~start_kernel-test-if-irqs-got-enabled-early-barf-and-disable-them-again
init/main.c
---
a/init/main.c~start_kernel-test-if-irqs-got-enabled-early-barf-and-disable-them-again
+++ a/init/main.c
@@ -538,6 +538,11 @@ asmlinkage void __init start_kernel(void
parse_args("Booting kernel", command_line, __start___param,
__stop___param - __start___param,
&unknown_bootoption);
+ if (!irqs_disabled()) {
+ printk(KERN_WARNING "start_kernel(): bug: interrupts were "
+ "enabled *very* early, fixing it\n");
+ local_irq_disable();
+ }
sort_main_extable();
trap_init();
rcu_init();
_
Patches currently in -mm which might be from [EMAIL PROTECTED] are
pci-prevent-down_read-when-pci_devices-is-empty.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
