2005-04-17 02:20:36 +04:00
/*
* linux / kernel / panic . c
*
* Copyright ( C ) 1991 , 1992 Linus Torvalds
*/
/*
* This function is used through - out the kernel ( including mm and fs )
* to indicate a major problem .
*/
2009-03-13 13:14:06 +03:00
# include <linux/debug_locks.h>
# include <linux/interrupt.h>
2009-10-16 16:09:18 +04:00
# include <linux/kmsg_dump.h>
2009-03-13 13:14:06 +03:00
# include <linux/kallsyms.h>
# include <linux/notifier.h>
2005-04-17 02:20:36 +04:00
# include <linux/module.h>
2009-03-13 13:14:06 +03:00
# include <linux/random.h>
2005-04-17 02:20:36 +04:00
# include <linux/reboot.h>
2009-03-13 13:14:06 +03:00
# include <linux/delay.h>
# include <linux/kexec.h>
# include <linux/sched.h>
2005-04-17 02:20:36 +04:00
# include <linux/sysrq.h>
2009-03-13 13:14:06 +03:00
# include <linux/init.h>
2005-04-17 02:20:36 +04:00
# include <linux/nmi.h>
2008-11-28 19:36:09 +03:00
# include <linux/dmi.h>
2005-04-17 02:20:36 +04:00
2010-08-11 05:03:28 +04:00
# define PANIC_TIMER_STEP 100
# define PANIC_BLINK_SPD 18
2005-04-17 02:20:36 +04:00
int panic_on_oops ;
2008-10-16 09:01:41 +04:00
static unsigned long tainted_mask ;
2006-03-23 14:00:57 +03:00
static int pause_on_oops ;
static int pause_on_oops_flag ;
static DEFINE_SPINLOCK ( pause_on_oops_lock ) ;
2005-04-17 02:20:36 +04:00
2006-03-23 14:00:57 +03:00
int panic_timeout ;
2005-04-17 02:20:36 +04:00
[PATCH] Notifier chain update: API changes
The kernel's implementation of notifier chains is unsafe. There is no
protection against entries being added to or removed from a chain while the
chain is in use. The issues were discussed in this thread:
http://marc.theaimsgroup.com/?l=linux-kernel&m=113018709002036&w=2
We noticed that notifier chains in the kernel fall into two basic usage
classes:
"Blocking" chains are always called from a process context
and the callout routines are allowed to sleep;
"Atomic" chains can be called from an atomic context and
the callout routines are not allowed to sleep.
We decided to codify this distinction and make it part of the API. Therefore
this set of patches introduces three new, parallel APIs: one for blocking
notifiers, one for atomic notifiers, and one for "raw" notifiers (which is
really just the old API under a new name). New kinds of data structures are
used for the heads of the chains, and new routines are defined for
registration, unregistration, and calling a chain. The three APIs are
explained in include/linux/notifier.h and their implementation is in
kernel/sys.c.
With atomic and blocking chains, the implementation guarantees that the chain
links will not be corrupted and that chain callers will not get messed up by
entries being added or removed. For raw chains the implementation provides no
guarantees at all; users of this API must provide their own protections. (The
idea was that situations may come up where the assumptions of the atomic and
blocking APIs are not appropriate, so it should be possible for users to
handle these things in their own way.)
There are some limitations, which should not be too hard to live with. For
atomic/blocking chains, registration and unregistration must always be done in
a process context since the chain is protected by a mutex/rwsem. Also, a
callout routine for a non-raw chain must not try to register or unregister
entries on its own chain. (This did happen in a couple of places and the code
had to be changed to avoid it.)
Since atomic chains may be called from within an NMI handler, they cannot use
spinlocks for synchronization. Instead we use RCU. The overhead falls almost
entirely in the unregister routine, which is okay since unregistration is much
less frequent that calling a chain.
Here is the list of chains that we adjusted and their classifications. None
of them use the raw API, so for the moment it is only a placeholder.
ATOMIC CHAINS
-------------
arch/i386/kernel/traps.c: i386die_chain
arch/ia64/kernel/traps.c: ia64die_chain
arch/powerpc/kernel/traps.c: powerpc_die_chain
arch/sparc64/kernel/traps.c: sparc64die_chain
arch/x86_64/kernel/traps.c: die_chain
drivers/char/ipmi/ipmi_si_intf.c: xaction_notifier_list
kernel/panic.c: panic_notifier_list
kernel/profile.c: task_free_notifier
net/bluetooth/hci_core.c: hci_notifier
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_chain
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_expect_chain
net/ipv6/addrconf.c: inet6addr_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_expect_chain
net/netlink/af_netlink.c: netlink_chain
BLOCKING CHAINS
---------------
arch/powerpc/platforms/pseries/reconfig.c: pSeries_reconfig_chain
arch/s390/kernel/process.c: idle_chain
arch/x86_64/kernel/process.c idle_notifier
drivers/base/memory.c: memory_chain
drivers/cpufreq/cpufreq.c cpufreq_policy_notifier_list
drivers/cpufreq/cpufreq.c cpufreq_transition_notifier_list
drivers/macintosh/adb.c: adb_client_list
drivers/macintosh/via-pmu.c sleep_notifier_list
drivers/macintosh/via-pmu68k.c sleep_notifier_list
drivers/macintosh/windfarm_core.c wf_client_list
drivers/usb/core/notify.c usb_notifier_list
drivers/video/fbmem.c fb_notifier_list
kernel/cpu.c cpu_chain
kernel/module.c module_notify_list
kernel/profile.c munmap_notifier
kernel/profile.c task_exit_notifier
kernel/sys.c reboot_notifier_list
net/core/dev.c netdev_chain
net/decnet/dn_dev.c: dnaddr_chain
net/ipv4/devinet.c: inetaddr_chain
It's possible that some of these classifications are wrong. If they are,
please let us know or submit a patch to fix them. Note that any chain that
gets called very frequently should be atomic, because the rwsem read-locking
used for blocking chains is very likely to incur cache misses on SMP systems.
(However, if the chain's callout routines may sleep then the chain cannot be
atomic.)
The patch set was written by Alan Stern and Chandra Seetharaman, incorporating
material written by Keith Owens and suggestions from Paul McKenney and Andrew
Morton.
[jes@sgi.com: restructure the notifier chain initialization macros]
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Jes Sorensen <jes@sgi.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-03-27 13:16:30 +04:00
ATOMIC_NOTIFIER_HEAD ( panic_notifier_list ) ;
2005-04-17 02:20:36 +04:00
EXPORT_SYMBOL ( panic_notifier_list ) ;
2010-08-11 05:03:28 +04:00
static long no_blink ( int state )
2010-03-06 00:42:55 +03:00
{
2010-08-11 05:03:28 +04:00
return 0 ;
2010-03-06 00:42:55 +03:00
}
2010-08-11 05:03:28 +04:00
/* Returns how long it waited in ms */
long ( * panic_blink ) ( int state ) ;
EXPORT_SYMBOL ( panic_blink ) ;
2005-04-17 02:20:36 +04:00
/**
* panic - halt the system
* @ fmt : The text string to print
*
* Display a message , then perform cleanups .
*
* This function never returns .
*/
NORET_TYPE void panic ( const char * fmt , . . . )
{
static char buf [ 1024 ] ;
va_list args ;
2010-08-11 05:03:28 +04:00
long i , i_next = 0 ;
int state = 0 ;
2005-04-17 02:20:36 +04:00
2005-06-26 01:57:52 +04:00
/*
2009-03-13 13:14:06 +03:00
* It ' s possible to come here directly from a panic - assertion and
* not have preempt disabled . Some functions called from here want
2005-06-26 01:57:52 +04:00
* preempt to be disabled . No point enabling it later though . . .
*/
preempt_disable ( ) ;
2010-05-27 01:44:24 +04:00
console_verbose ( ) ;
2005-04-17 02:20:36 +04:00
bust_spinlocks ( 1 ) ;
va_start ( args , fmt ) ;
vsnprintf ( buf , sizeof ( buf ) , fmt , args ) ;
va_end ( args ) ;
printk ( KERN_EMERG " Kernel panic - not syncing: %s \n " , buf ) ;
2008-02-14 11:07:01 +03:00
# ifdef CONFIG_DEBUG_BUGVERBOSE
dump_stack ( ) ;
# endif
2005-04-17 02:20:36 +04:00
2005-06-26 01:57:52 +04:00
/*
* If we have crashed and we have a crash kernel loaded let it handle
* everything else .
* Do we want to call this before we try to display a message ?
*/
2005-06-26 01:58:26 +04:00
crash_kexec ( NULL ) ;
2005-06-26 01:57:52 +04:00
2009-12-22 06:15:43 +03:00
kmsg_dump ( KMSG_DUMP_PANIC ) ;
2005-06-26 01:57:52 +04:00
/*
* Note smp_send_stop is the usual smp shutdown function , which
* unfortunately means it may not be hardened to work in a panic
* situation .
*/
2005-04-17 02:20:36 +04:00
smp_send_stop ( ) ;
[PATCH] Notifier chain update: API changes
The kernel's implementation of notifier chains is unsafe. There is no
protection against entries being added to or removed from a chain while the
chain is in use. The issues were discussed in this thread:
http://marc.theaimsgroup.com/?l=linux-kernel&m=113018709002036&w=2
We noticed that notifier chains in the kernel fall into two basic usage
classes:
"Blocking" chains are always called from a process context
and the callout routines are allowed to sleep;
"Atomic" chains can be called from an atomic context and
the callout routines are not allowed to sleep.
We decided to codify this distinction and make it part of the API. Therefore
this set of patches introduces three new, parallel APIs: one for blocking
notifiers, one for atomic notifiers, and one for "raw" notifiers (which is
really just the old API under a new name). New kinds of data structures are
used for the heads of the chains, and new routines are defined for
registration, unregistration, and calling a chain. The three APIs are
explained in include/linux/notifier.h and their implementation is in
kernel/sys.c.
With atomic and blocking chains, the implementation guarantees that the chain
links will not be corrupted and that chain callers will not get messed up by
entries being added or removed. For raw chains the implementation provides no
guarantees at all; users of this API must provide their own protections. (The
idea was that situations may come up where the assumptions of the atomic and
blocking APIs are not appropriate, so it should be possible for users to
handle these things in their own way.)
There are some limitations, which should not be too hard to live with. For
atomic/blocking chains, registration and unregistration must always be done in
a process context since the chain is protected by a mutex/rwsem. Also, a
callout routine for a non-raw chain must not try to register or unregister
entries on its own chain. (This did happen in a couple of places and the code
had to be changed to avoid it.)
Since atomic chains may be called from within an NMI handler, they cannot use
spinlocks for synchronization. Instead we use RCU. The overhead falls almost
entirely in the unregister routine, which is okay since unregistration is much
less frequent that calling a chain.
Here is the list of chains that we adjusted and their classifications. None
of them use the raw API, so for the moment it is only a placeholder.
ATOMIC CHAINS
-------------
arch/i386/kernel/traps.c: i386die_chain
arch/ia64/kernel/traps.c: ia64die_chain
arch/powerpc/kernel/traps.c: powerpc_die_chain
arch/sparc64/kernel/traps.c: sparc64die_chain
arch/x86_64/kernel/traps.c: die_chain
drivers/char/ipmi/ipmi_si_intf.c: xaction_notifier_list
kernel/panic.c: panic_notifier_list
kernel/profile.c: task_free_notifier
net/bluetooth/hci_core.c: hci_notifier
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_chain
net/ipv4/netfilter/ip_conntrack_core.c: ip_conntrack_expect_chain
net/ipv6/addrconf.c: inet6addr_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_chain
net/netfilter/nf_conntrack_core.c: nf_conntrack_expect_chain
net/netlink/af_netlink.c: netlink_chain
BLOCKING CHAINS
---------------
arch/powerpc/platforms/pseries/reconfig.c: pSeries_reconfig_chain
arch/s390/kernel/process.c: idle_chain
arch/x86_64/kernel/process.c idle_notifier
drivers/base/memory.c: memory_chain
drivers/cpufreq/cpufreq.c cpufreq_policy_notifier_list
drivers/cpufreq/cpufreq.c cpufreq_transition_notifier_list
drivers/macintosh/adb.c: adb_client_list
drivers/macintosh/via-pmu.c sleep_notifier_list
drivers/macintosh/via-pmu68k.c sleep_notifier_list
drivers/macintosh/windfarm_core.c wf_client_list
drivers/usb/core/notify.c usb_notifier_list
drivers/video/fbmem.c fb_notifier_list
kernel/cpu.c cpu_chain
kernel/module.c module_notify_list
kernel/profile.c munmap_notifier
kernel/profile.c task_exit_notifier
kernel/sys.c reboot_notifier_list
net/core/dev.c netdev_chain
net/decnet/dn_dev.c: dnaddr_chain
net/ipv4/devinet.c: inetaddr_chain
It's possible that some of these classifications are wrong. If they are,
please let us know or submit a patch to fix them. Note that any chain that
gets called very frequently should be atomic, because the rwsem read-locking
used for blocking chains is very likely to incur cache misses on SMP systems.
(However, if the chain's callout routines may sleep then the chain cannot be
atomic.)
The patch set was written by Alan Stern and Chandra Seetharaman, incorporating
material written by Keith Owens and suggestions from Paul McKenney and Andrew
Morton.
[jes@sgi.com: restructure the notifier chain initialization macros]
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Jes Sorensen <jes@sgi.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-03-27 13:16:30 +04:00
atomic_notifier_call_chain ( & panic_notifier_list , 0 , buf ) ;
2005-04-17 02:20:36 +04:00
2009-10-02 15:41:20 +04:00
bust_spinlocks ( 0 ) ;
2010-08-11 05:03:28 +04:00
if ( ! panic_blink )
panic_blink = no_blink ;
2005-06-26 01:57:52 +04:00
if ( panic_timeout > 0 ) {
2005-04-17 02:20:36 +04:00
/*
2009-03-13 13:14:06 +03:00
* Delay timeout seconds before rebooting the machine .
* We can ' t use the " normal " timers since we just panicked .
*/
printk ( KERN_EMERG " Rebooting in %d seconds.. " , panic_timeout ) ;
2010-08-11 05:03:28 +04:00
for ( i = 0 ; i < panic_timeout * 1000 ; i + = PANIC_TIMER_STEP ) {
2005-04-17 02:20:36 +04:00
touch_nmi_watchdog ( ) ;
2010-08-11 05:03:28 +04:00
if ( i > = i_next ) {
i + = panic_blink ( state ^ = 1 ) ;
i_next = i + 3600 / PANIC_BLINK_SPD ;
}
mdelay ( PANIC_TIMER_STEP ) ;
2005-04-17 02:20:36 +04:00
}
2009-03-13 13:14:06 +03:00
/*
* This will not be a clean reboot , with everything
* shutting down . But if there is a chance of
* rebooting the system it will be rebooted .
2005-04-17 02:20:36 +04:00
*/
2005-07-26 21:49:23 +04:00
emergency_restart ( ) ;
2005-04-17 02:20:36 +04:00
}
# ifdef __sparc__
{
extern int stop_a_enabled ;
2005-04-25 07:38:02 +04:00
/* Make sure the user can actually press Stop-A (L1-A) */
2005-04-17 02:20:36 +04:00
stop_a_enabled = 1 ;
2005-04-25 07:38:02 +04:00
printk ( KERN_EMERG " Press Stop-A (L1-A) to return to the boot prom \n " ) ;
2005-04-17 02:20:36 +04:00
}
# endif
2006-01-06 11:19:28 +03:00
# if defined(CONFIG_S390)
2009-03-13 13:14:06 +03:00
{
unsigned long caller ;
caller = ( unsigned long ) __builtin_return_address ( 0 ) ;
disabled_wait ( caller ) ;
}
2005-04-17 02:20:36 +04:00
# endif
local_irq_enable ( ) ;
2010-08-11 05:03:28 +04:00
for ( i = 0 ; ; i + = PANIC_TIMER_STEP ) {
2006-02-10 12:51:11 +03:00
touch_softlockup_watchdog ( ) ;
2010-08-11 05:03:28 +04:00
if ( i > = i_next ) {
i + = panic_blink ( state ^ = 1 ) ;
i_next = i + 3600 / PANIC_BLINK_SPD ;
}
mdelay ( PANIC_TIMER_STEP ) ;
2005-04-17 02:20:36 +04:00
}
}
EXPORT_SYMBOL ( panic ) ;
2007-10-18 14:06:08 +04:00
2008-10-16 09:01:41 +04:00
struct tnt {
2009-03-13 13:14:06 +03:00
u8 bit ;
char true ;
char false ;
2008-10-16 09:01:41 +04:00
} ;
static const struct tnt tnts [ ] = {
2009-03-13 13:14:06 +03:00
{ TAINT_PROPRIETARY_MODULE , ' P ' , ' G ' } ,
{ TAINT_FORCED_MODULE , ' F ' , ' ' } ,
{ TAINT_UNSAFE_SMP , ' S ' , ' ' } ,
{ TAINT_FORCED_RMMOD , ' R ' , ' ' } ,
{ TAINT_MACHINE_CHECK , ' M ' , ' ' } ,
{ TAINT_BAD_PAGE , ' B ' , ' ' } ,
{ TAINT_USER , ' U ' , ' ' } ,
{ TAINT_DIE , ' D ' , ' ' } ,
{ TAINT_OVERRIDDEN_ACPI_TABLE , ' A ' , ' ' } ,
{ TAINT_WARN , ' W ' , ' ' } ,
{ TAINT_CRAP , ' C ' , ' ' } ,
2010-04-03 22:36:42 +04:00
{ TAINT_FIRMWARE_WORKAROUND , ' I ' , ' ' } ,
2008-10-16 09:01:41 +04:00
} ;
2005-04-17 02:20:36 +04:00
/**
* print_tainted - return a string to represent the kernel taint state .
*
* ' P ' - Proprietary module has been loaded .
* ' F ' - Module has been forcibly loaded .
* ' S ' - SMP with CPUs not designed for SMP .
* ' R ' - User forced a module unload .
2007-10-20 02:30:06 +04:00
* ' M ' - System experienced a machine check exception .
2005-04-17 02:20:36 +04:00
* ' B ' - System has hit bad_page .
2007-02-10 12:45:24 +03:00
* ' U ' - Userspace - defined naughtiness .
2008-12-02 00:14:00 +03:00
* ' D ' - Kernel has oopsed before
2008-04-29 11:58:39 +04:00
* ' A ' - ACPI table overridden .
* ' W ' - Taint on warning .
2008-09-25 01:46:44 +04:00
* ' C ' - modules from drivers / staging are loaded .
2010-04-03 22:36:42 +04:00
* ' I ' - Working around severe firmware bug .
2005-04-17 02:20:36 +04:00
*
2009-06-29 05:10:07 +04:00
* The string is overwritten by the next call to print_tainted ( ) .
2005-04-17 02:20:36 +04:00
*/
const char * print_tainted ( void )
{
2008-10-16 09:01:41 +04:00
static char buf [ ARRAY_SIZE ( tnts ) + sizeof ( " Tainted: " ) + 1 ] ;
if ( tainted_mask ) {
char * s ;
int i ;
s = buf + sprintf ( buf , " Tainted: " ) ;
for ( i = 0 ; i < ARRAY_SIZE ( tnts ) ; i + + ) {
const struct tnt * t = & tnts [ i ] ;
* s + + = test_bit ( t - > bit , & tainted_mask ) ?
t - > true : t - > false ;
}
* s = 0 ;
} else
2005-04-17 02:20:36 +04:00
snprintf ( buf , sizeof ( buf ) , " Not tainted " ) ;
2009-03-13 13:14:06 +03:00
return buf ;
2005-04-17 02:20:36 +04:00
}
2008-10-16 09:01:41 +04:00
int test_taint ( unsigned flag )
2005-04-17 02:20:36 +04:00
{
2008-10-16 09:01:41 +04:00
return test_bit ( flag , & tainted_mask ) ;
}
EXPORT_SYMBOL ( test_taint ) ;
unsigned long get_taint ( void )
{
return tainted_mask ;
2005-04-17 02:20:36 +04:00
}
2006-03-23 14:00:57 +03:00
2005-04-17 02:20:36 +04:00
void add_taint ( unsigned flag )
2006-03-23 14:00:57 +03:00
{
2009-04-11 05:17:17 +04:00
/*
* Can ' t trust the integrity of the kernel anymore .
* We don ' t call directly debug_locks_off ( ) because the issue
* is not necessarily serious enough to set oops_in_progress to 1
2009-04-11 05:17:18 +04:00
* Also we want to keep up lockdep for staging development and
* post - warning case .
2009-04-11 05:17:17 +04:00
*/
2009-04-11 05:17:18 +04:00
if ( flag ! = TAINT_CRAP & & flag ! = TAINT_WARN & & __debug_locks_off ( ) )
2009-04-23 11:36:52 +04:00
printk ( KERN_WARNING " Disabling lock debugging due to kernel taint \n " ) ;
2009-04-11 05:17:17 +04:00
2008-10-16 09:01:41 +04:00
set_bit ( flag , & tainted_mask ) ;
2006-03-23 14:00:57 +03:00
}
2005-04-17 02:20:36 +04:00
EXPORT_SYMBOL ( add_taint ) ;
2006-03-23 14:00:57 +03:00
static void spin_msec ( int msecs )
{
int i ;
for ( i = 0 ; i < msecs ; i + + ) {
touch_nmi_watchdog ( ) ;
mdelay ( 1 ) ;
}
}
/*
* It just happens that oops_enter ( ) and oops_exit ( ) are identically
* implemented . . .
*/
static void do_oops_enter_exit ( void )
{
unsigned long flags ;
static int spin_counter ;
if ( ! pause_on_oops )
return ;
spin_lock_irqsave ( & pause_on_oops_lock , flags ) ;
if ( pause_on_oops_flag = = 0 ) {
/* This CPU may now print the oops message */
pause_on_oops_flag = 1 ;
} else {
/* We need to stall this CPU */
if ( ! spin_counter ) {
/* This CPU gets to do the counting */
spin_counter = pause_on_oops ;
do {
spin_unlock ( & pause_on_oops_lock ) ;
spin_msec ( MSEC_PER_SEC ) ;
spin_lock ( & pause_on_oops_lock ) ;
} while ( - - spin_counter ) ;
pause_on_oops_flag = 0 ;
} else {
/* This CPU waits for a different one */
while ( spin_counter ) {
spin_unlock ( & pause_on_oops_lock ) ;
spin_msec ( 1 ) ;
spin_lock ( & pause_on_oops_lock ) ;
}
}
}
spin_unlock_irqrestore ( & pause_on_oops_lock , flags ) ;
}
/*
2009-03-13 13:14:06 +03:00
* Return true if the calling CPU is allowed to print oops - related info .
* This is a bit racy . .
2006-03-23 14:00:57 +03:00
*/
int oops_may_print ( void )
{
return pause_on_oops_flag = = 0 ;
}
/*
* Called when the architecture enters its oops handler , before it prints
2009-03-13 13:14:06 +03:00
* anything . If this is the first CPU to oops , and it ' s oopsing the first
* time then let it proceed .
2006-03-23 14:00:57 +03:00
*
2009-03-13 13:14:06 +03:00
* This is all enabled by the pause_on_oops kernel boot option . We do all
* this to ensure that oopses don ' t scroll off the screen . It has the
* side - effect of preventing later - oopsing CPUs from mucking up the display ,
* too .
2006-03-23 14:00:57 +03:00
*
2009-03-13 13:14:06 +03:00
* It turns out that the CPU which is allowed to print ends up pausing for
* the right duration , whereas all the other CPUs pause for twice as long :
* once in oops_enter ( ) , once in oops_exit ( ) .
2006-03-23 14:00:57 +03:00
*/
void oops_enter ( void )
{
2009-07-24 23:30:45 +04:00
tracing_off ( ) ;
2009-03-13 13:14:06 +03:00
/* can't trust the integrity of the kernel anymore: */
debug_locks_off ( ) ;
2006-03-23 14:00:57 +03:00
do_oops_enter_exit ( ) ;
}
2007-12-20 17:01:17 +03:00
/*
* 64 - bit random ID for oopses :
*/
static u64 oops_id ;
static int init_oops_id ( void )
{
if ( ! oops_id )
get_random_bytes ( & oops_id , sizeof ( oops_id ) ) ;
2009-01-07 01:40:54 +03:00
else
oops_id + + ;
2007-12-20 17:01:17 +03:00
return 0 ;
}
late_initcall ( init_oops_id ) ;
2008-01-30 15:32:50 +03:00
static void print_oops_end_marker ( void )
{
init_oops_id ( ) ;
printk ( KERN_WARNING " ---[ end trace %016llx ]--- \n " ,
( unsigned long long ) oops_id ) ;
}
2006-03-23 14:00:57 +03:00
/*
* Called when the architecture exits its oops handler , after printing
* everything .
*/
void oops_exit ( void )
{
do_oops_enter_exit ( ) ;
2008-01-30 15:32:50 +03:00
print_oops_end_marker ( ) ;
2009-10-16 16:09:18 +04:00
kmsg_dump ( KMSG_DUMP_OOPS ) ;
2006-03-23 14:00:57 +03:00
}
2006-09-26 12:52:39 +04:00
2008-01-30 15:32:50 +03:00
# ifdef WANT_WARN_ON_SLOWPATH
2009-05-17 00:41:28 +04:00
struct slowpath_args {
const char * fmt ;
2008-07-25 12:45:53 +04:00
va_list args ;
2009-05-17 00:41:28 +04:00
} ;
2008-11-28 19:36:09 +03:00
2010-04-03 22:34:56 +04:00
static void warn_slowpath_common ( const char * file , int line , void * caller ,
unsigned taint , struct slowpath_args * args )
2009-05-17 00:41:28 +04:00
{
const char * board ;
2008-07-25 12:45:53 +04:00
printk ( KERN_WARNING " ------------[ cut here ]------------ \n " ) ;
2009-05-17 00:41:28 +04:00
printk ( KERN_WARNING " WARNING: at %s:%d %pS() \n " , file , line , caller ) ;
2008-11-28 19:36:09 +03:00
board = dmi_get_system_info ( DMI_PRODUCT_NAME ) ;
if ( board )
printk ( KERN_WARNING " Hardware name: %s \n " , board ) ;
2008-11-28 19:35:25 +03:00
2009-05-17 00:41:28 +04:00
if ( args )
vprintk ( args - > fmt , args - > args ) ;
2008-07-25 12:45:53 +04:00
print_modules ( ) ;
dump_stack ( ) ;
print_oops_end_marker ( ) ;
2010-04-03 22:34:56 +04:00
add_taint ( taint ) ;
2008-07-25 12:45:53 +04:00
}
2009-05-17 00:41:28 +04:00
void warn_slowpath_fmt ( const char * file , int line , const char * fmt , . . . )
{
struct slowpath_args args ;
args . fmt = fmt ;
va_start ( args . args , fmt ) ;
2010-04-03 22:34:56 +04:00
warn_slowpath_common ( file , line , __builtin_return_address ( 0 ) ,
TAINT_WARN , & args ) ;
2009-05-17 00:41:28 +04:00
va_end ( args . args ) ;
}
2009-05-07 03:02:53 +04:00
EXPORT_SYMBOL ( warn_slowpath_fmt ) ;
2010-04-03 22:34:56 +04:00
void warn_slowpath_fmt_taint ( const char * file , int line ,
unsigned taint , const char * fmt , . . . )
{
struct slowpath_args args ;
args . fmt = fmt ;
va_start ( args . args , fmt ) ;
warn_slowpath_common ( file , line , __builtin_return_address ( 0 ) ,
taint , & args ) ;
va_end ( args . args ) ;
}
EXPORT_SYMBOL ( warn_slowpath_fmt_taint ) ;
2009-05-07 03:02:53 +04:00
void warn_slowpath_null ( const char * file , int line )
{
2010-04-03 22:34:56 +04:00
warn_slowpath_common ( file , line , __builtin_return_address ( 0 ) ,
TAINT_WARN , NULL ) ;
2009-05-07 03:02:53 +04:00
}
EXPORT_SYMBOL ( warn_slowpath_null ) ;
2008-01-30 15:32:50 +03:00
# endif
2006-09-26 12:52:39 +04:00
# ifdef CONFIG_CC_STACKPROTECTOR
2008-02-16 02:33:12 +03:00
2006-09-26 12:52:39 +04:00
/*
* Called when gcc ' s - fstack - protector feature is used , and
* gcc detects corruption of the on - stack canary value
*/
void __stack_chk_fail ( void )
{
2008-02-14 11:02:13 +03:00
panic ( " stack-protector: Kernel stack is corrupted in: %p \n " ,
__builtin_return_address ( 0 ) ) ;
2006-09-26 12:52:39 +04:00
}
EXPORT_SYMBOL ( __stack_chk_fail ) ;
2008-02-16 02:33:12 +03:00
2006-09-26 12:52:39 +04:00
# endif
2008-10-22 19:00:24 +04:00
core_param ( panic , panic_timeout , int , 0644 ) ;
core_param ( pause_on_oops , pause_on_oops , int , 0644 ) ;