Re: fault-injection framework on ia64

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> I couldn't understand this build error happend.
> (I might misunderstand something)
> Because IA64 config always disable CONFIG_STACKTRACE, so
> should_fail() doesn't use save_stack_trace() in fail_stacktrace().

OK.  Maybe this patch broke things:


From: "Paolo 'Blaisorblade' Giarrusso" <blaisorblade@xxxxxxxx>

There is no prompt for STACKTRACE, so it is enabled only when 'select'ed.
FAULT_INJECTION depends on it, while LOCKDEP selects it.  So
FAULT_INJECTION becomes visible in Kconfig only when LOCKDEP is enabled.


I see. I'll make sub-option for fault injection to enable/disable stacktrace.
It'll fix IA64 build problem and unvisible FAULT_INJECTION without LOCKDEP.
-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Sparc Linux]     [DCCP]     [Linux ARM]     [Yosemite News]     [Linux SCSI]     [Linux x86_64]     [Linux for Ham Radio]

  Powered by Linux