x86, mce: machine check recovery for applications [updated]
Subsystems (7)
PATCH 1/6 HWPOISON: clean up memory_failure() vs. __memory_failure()
In reply to Tony LuckThere is only one caller of memory_failure(), all other users call __memory_failure() and pass in the flags argument explicitly. The lone user of memory_failure() will soon need to pass flags too.
Add flags argument to the callsite in mce.c. Delete the old memory_failure() function, and then rename __memory_failure() without the leading "__".
Provide clearer message when action optional memory errors are ignored.
--- arch/x86/kernel/cpu/mcheck/mce.c | 12 ++++++--- drivers/base/memory.c | 2 +- include/linux/mm.h | 3 +- mm/hwpoison-inject.c | 4 +- mm/madvise.c | 2 +- mm/memory-failure.c | 46 +++++++++++++++++-------------------- 6 files changed, 34 insertions(+), 35 deletions(-)
arch/x86/kernel/cpu/mcheck/mce.c +8 -4
@@ -1046,11 +1046,15 @@ out: }EXPORT_SYMBOL_GPL (do_machine_check); -/* dummy to break dependency. actual code is in mm/memory-failure.c */ -void __attribute__((weak))memory_failure (unsigned long pfn,int vector) +#ifndef CONFIG_MEMORY_FAILURE +int memory_failure (unsigned long pfn,int vector,int flags) { -printk (KERN_ERR "Action optional memory failure at %lx ignored\n" , pfn); +printk (KERN_ERR "Uncorrected memory error in page 0x%lx ignored\n" +"Rebuild kernel with CONFIG_MEMORY_FAILURE=y for smarter handling\n" , pfn); + +return 0 ; } +#endif /* * Called after mce notification in process context. This code
@@ -1068,7 +1072,7 @@ void mce_notify_process(void)unsigned long pfn;mce_notify_irq ();while (mce_ring_get (&pfn)) -memory_failure (pfn,MCE_VECTOR ); +memory_failure (pfn,MCE_VECTOR ,0 ); }static void mce_process_work (struct work_struct *dummy)
drivers/base/memory.c +1 -1
@@ -474,7 +474,7 @@ store_hard_offline_page(struct class *class,if (strict_strtoull (buf,0 , &pfn) <0 )return -EINVAL ; pfn >>=PAGE_SHIFT ; - ret =__memory_failure (pfn,0 ,0 ); + ret =memory_failure (pfn,0 ,0 );return ret ? ret : count; }
include/linux/mm.h +1 -2
@@ -1607,8 +1607,7 @@ void vmemmap_populate_print_last(void);enum mf_flags {MF_COUNT_INCREASED =1 <<0 , }; -extern void memory_failure (unsigned long pfn,int trapno); -extern int __memory_failure (unsigned long pfn,int trapno,int flags); +extern int memory_failure (unsigned long pfn,int trapno,int flags);extern void memory_failure_queue (unsigned long pfn,int trapno,int flags);extern int unpoison_memory (unsigned long pfn);extern int sysctl_memory_failure_early_kill;
mm/hwpoison-inject.c +2 -2
@@ -45,7 +45,7 @@ static int hwpoison_inject(void *data, u64 val)* do a racy check with elevated page count, to make sure PG_hwpoison * will only be set for the targeted owner (or on a free page). * We temporarily take page lock for try_get_mem_cgroup_from_page(). -* __memory_failure() will redo the check reliably inside page lock. +* memory_failure() will redo the check reliably inside page lock. */ lock_page (hpage); err =hwpoison_filter (hpage);
@@ -55,7 +55,7 @@ static int hwpoison_inject(void *data, u64 val) inject:printk (KERN_INFO "Injecting memory failure at pfn %lx\n" , pfn); -return __memory_failure (pfn,18 ,MF_COUNT_INCREASED ); +return memory_failure (pfn,18 ,MF_COUNT_INCREASED ); }static int hwpoison_unpoison (void *data,u64 val)
mm/madvise.c +1 -1
@@ -251,7 +251,7 @@ static int madvise_hwpoison(int bhv, unsigned long start, unsigned long end)printk (KERN_INFO "Injecting memory failure for page %lx at %lx\n" ,page_to_pfn (p), start);/* Ignore return value for now */ -__memory_failure (page_to_pfn (p),0 ,MF_COUNT_INCREASED ); +memory_failure (page_to_pfn (p),0 ,MF_COUNT_INCREASED ); }return ret; }
mm/memory-failure.c +21 -25
64 lines not on this page · raw message
Signature · 1 line
1.7.3.1
cover x86, mce: machine check recovery for applications [updated]
machine check recovery - updates since December 13th version
part1:
Change printk from:
Action optional memory failure at %lx ignored
to:
Uncorrected memory error in page 0x%lx ignored Rebuild kernel with CONFIG_MEMORY_FAILURE=y for smarter handling
part3:
Fix spelling of granularity.
Add Boris' ACK line
part4:
Some code style fixes from Ingo
Use "struct mce_info *" as iterator in mce_{save,find}_info(). Make mce_find_info() return pointer, so mce_clear_info() becomes trivial
part5:
Update comments in several places to reflect changes for recovery
part2: part6:
Code unchanged - Added Boris' ACK line
Tony Luck (6):
HWPOISON: clean up memory_failure() vs. __memory_failure()
HWPOISON: Add code to handle "action required" errors. x86, mce: create helper function to save addr/misc when needed x86, mce: Add mechanism to safely save information in MCE handler x86, mce: handle "action required" errors
x86, mce: Recognise machine check bank signature for data path error
arch/x86/kernel/cpu/mcheck/mce-severity.c | 14 +++- arch/x86/kernel/cpu/mcheck/mce.c | 155 ++++++++++++++++++++++------- drivers/base/memory.c | 2 +- include/linux/mm.h | 4 +- mm/hwpoison-inject.c | 4 +- mm/madvise.c | 2 +- mm/memory-failure.c | 96 +++++++++--------- 7 files changed, 187 insertions(+), 90 deletions(-)
Signature · 1 line
1.7.3.1
PATCH 2/6 HWPOISON: Add code to handle "action required" errors.
Add new flag bit "MF_ACTION_REQUIRED" to be used by machine check code to force a signal with si_code = BUS_MCEERR_AR in the case where the error occurs in processor execution context. Pass the flags argument along call chain:
memory_failure() hwpoison_user_mappings() kill_procs() kill_proc()
Drop the "_ao" suffix from kill_procs_ao() and kill_proc_ao() since they can now handle "action required" as well as "action optional" errors.
--- include/linux/mm.h | 1 + mm/memory-failure.c | 50 +++++++++++++++++++++++++++++--------------------- 2 files changed, 30 insertions(+), 21 deletions(-)
include/linux/mm.h +1 -0
@@ -1606,6 +1606,7 @@ void vmemmap_populate_print_last(void);enum mf_flags {MF_COUNT_INCREASED =1 <<0 , +MF_ACTION_REQUIRED =1 <<1 , };extern int memory_failure (unsigned long pfn,int trapno,int flags);extern void memory_failure_queue (unsigned long pfn,int trapno,int flags);
mm/memory-failure.c +29 -21
100 lines not on this page · raw message
Signature · 1 line
1.7.3.1
PATCH 3/6 x86, mce: create helper function to save addr/misc when needed
In reply to Tony LuckThe MCI_STATUS_MISCV and MCI_STATUS_ADDRV bits in the bank status registers define whether the MISC and ADDR registers respectively contain valid data - provide a helper function to check these bits and read the registers when needed.
In addition, processors that support software error recovery (as indicated by the MCG_SER_P bit in the MCG_CAP register) may include some undefined bits in the ADDR register - mask these out.
--- arch/x86/kernel/cpu/mcheck/mce.c | 31 +++++++++++++++++++++++-------- 1 files changed, 23 insertions(+), 8 deletions(-)
arch/x86/kernel/cpu/mcheck/mce.c +23 -8
@@ -492,6 +492,27 @@ static void mce_report_event(struct pt_regs *regs)irq_work_queue (&__get_cpu_var (mce_irq_work)); } +/* +* Read ADDR and MISC registers. +*/ +static void mce_read_aux (struct mce *m,int i) +{ +if (m->status &MCI_STATUS_MISCV ) + m->misc =mce_rdmsrl (MSR_IA32_MCx_MISC (i)); +if (m->status &MCI_STATUS_ADDRV ) { + m->addr =mce_rdmsrl (MSR_IA32_MCx_ADDR (i)); + +/* +* Mask the reported address by the reported granularity. +*/ +if (mce_ser && (m->status &MCI_STATUS_MISCV )) { +u8 shift = m->misc &0x3f ; + m->addr >>= shift; + m->addr <<= shift; + } + } +} +DEFINE_PER_CPU (unsigned, mce_poll_count);/*
@@ -542,10 +563,7 @@ void machine_check_poll(enum mcp_flags flags, mce_banks_t *b) (m.status & (mce_ser ? MCI_STATUS_S : MCI_STATUS_UC))) continue; -if (m.status &MCI_STATUS_MISCV ) - m.misc =mce_rdmsrl (MSR_IA32_MCx_MISC (i)); -if (m.status &MCI_STATUS_ADDRV ) - m.addr =mce_rdmsrl (MSR_IA32_MCx_ADDR (i)); +mce_read_aux (&m, i);if (!(flags &MCP_TIMESTAMP )) m.tsc =0 ;
@@ -981,10 +999,7 @@ void do_machine_check(struct pt_regs *regs, long error_code)if (severity ==MCE_AR_SEVERITY ) kill_it =1 ; -if (m.status &MCI_STATUS_MISCV ) - m.misc =mce_rdmsrl (MSR_IA32_MCx_MISC (i)); -if (m.status &MCI_STATUS_ADDRV ) - m.addr =mce_rdmsrl (MSR_IA32_MCx_ADDR (i)); +mce_read_aux (&m, i);/* * Action optional error. Queue address for later processing.
Signature · 1 line
1.7.3.1
PATCH 5/6 x86, mce: handle "action required" errors
In reply to Tony LuckAll non-urgent actions (reporting low severity errors and handling "action-optional" errors) are now handled by a work queue. This means that TIF_MCE_NOTIFY can be used to block execution for a thread experiencing an "action-required" fault until we get all cpus out of the machine check handler (and the thread that hit the fault into mce_notify_process().
We use the new mce_{save,find,clear}_info() API to get information from do_machine_check() to mce_notify_process(), and then use the newly improved memory_failure(..., MF_ACTION_REQUIRED) to handle the error (possibly signalling the process).
Update some comments to make the new code flows clearer.
--- arch/x86/kernel/cpu/mcheck/mce.c | 70 ++++++++++++++++++++++++-------------- 1 files changed, 44 insertions(+), 26 deletions(-)
arch/x86/kernel/cpu/mcheck/mce.c +44 -26
@@ -1036,12 +1036,6 @@ void do_machine_check(struct pt_regs *regs, long error_code)continue ; } -/* -* Kill on action required. -*/ -if (severity ==MCE_AR_SEVERITY ) - kill_it =1 ; -mce_read_aux (&m, i);/*
@@ -1062,6 +1056,8 @@ void do_machine_check(struct pt_regs *regs, long error_code) } } + m = *final; +if (!no_way_out)mce_clear_state (toclear);
@@ -1080,7 +1076,7 @@ void do_machine_check(struct pt_regs *regs, long error_code)* support MCE broadcasting or it has been disabled. */ if (no_way_out && tolerant <3 ) -mce_panic ("Fatal machine check on current CPU" , final, msg); +mce_panic ("Fatal machine check on current CPU" , &m, msg);/* * If the error seems to be unrecoverable, something should be
@@ -1089,11 +1085,13 @@ void do_machine_check(struct pt_regs *regs, long error_code)* high, don't try to do anything at all. */ -if (kill_it && tolerant <3 ) +if (worst !=MCE_AR_SEVERITY && kill_it && tolerant <3 )force_sig (SIGBUS , current); -/* notify userspace ASAP */ -set_thread_flag (TIF_MCE_NOTIFY ); +if (worst ==MCE_AR_SEVERITY ) { +mce_save_info (m.addr); +set_thread_flag (TIF_MCE_NOTIFY ); + }if (worst >0 )mce_report_event (regs);
@@ -1107,34 +1105,56 @@ EXPORT_SYMBOL_GPL(do_machine_check);#ifndef CONFIG_MEMORY_FAILURE int memory_failure (unsigned long pfn,int vector,int flags) { -printk (KERN_ERR "Action optional memory failure at %lx ignored\n" , pfn); +if (flags &MF_ACTION_REQUIRED ) +return -ENXIO ;/* panic? */ +else +printk (KERN_ERR "Action optional memory failure at %lx ignored\n" , pfn);return 0 ; }#endif /* -* Called after mce notification in process context. This code -* is allowed to sleep. Call the high level VM handler to process -* any corrupted pages. -* Assume that the work queue code only calls this one at a time -* per CPU. -* Note we don't disable preemption, so this code might run on the wrong -* CPU. In this case the event is picked up by the scheduled work queue. -* This is merely a fast path to expedite processing in some common -* cases. +* Called in process context that interrupted by MCE and marked with +* TIF_MCE_NOTFY, just before returning to errorneous userland. +* This code is allowed to sleep. +* Attempt possible recovery such as calling the high level VM handler to +* process any corrupted pages, and kill/signal current process if required. +* Action required errors are handled here. */ void mce_notify_process (void ) {unsigned long pfn; -mce_notify_irq (); -while (mce_ring_get (&pfn)) -memory_failure (pfn,MCE_VECTOR ,0 ); +struct mce_info *mi =mce_find_info (); + +if (!mi) +mce_panic ("Lost address" ,NULL ,NULL ); + pfn = mi->paddr >>PAGE_SHIFT ; + +clear_thread_flag (TIF_MCE_NOTIFY ); + +pr_err ("Uncorrected hardware memory error in user-access at %llx" , + mi->paddr); +if (memory_failure (pfn,MCE_VECTOR ,MF_ACTION_REQUIRED ) <0 ) { +pr_err ("Memory error not recovered" ); +force_sig (SIGBUS , current); + }else { +pr_err ("Memory error recovered" ); + } +mce_clear_info (mi); } +/* +* Action optional processing happens here (picking up +* from the list of faulting pages that do_machine_check() +* placed into the "ring"). +*/ static void mce_process_work (struct work_struct *dummy) { -mce_notify_process (); +unsigned long pfn; + +while (mce_ring_get (&pfn)) +memory_failure (pfn,MCE_VECTOR ,0 ); }#ifdef CONFIG_X86_MCE_INTEL
@@ -1224,8 +1244,6 @@ int mce_notify_irq(void)/* Not more than two messages every minute */ static DEFINE_RATELIMIT_STATE(ratelimit, 60*HZ, 2); -clear_thread_flag (TIF_MCE_NOTIFY ); -if (test_and_clear_bit (0 , &mce_need_notify)) {/* wake processes polling /dev/mcelog */ wake_up_interruptible (&mce_chrdev_wait);
--
1.7.3.1
--- arch/x86/kernel/cpu/mcheck/mce.c | 71 ++++++++++++++++++++++++-------------- 1 files changed, 45 insertions(+), 26 deletions(-)
arch/x86/kernel/cpu/mcheck/mce.c +45 -26
129 lines not on this page · raw message
Signature · 1 line
1.7.3.1
PATCH 6/6 x86, mce: Recognise machine check bank signature for data path error
In reply to Tony LuckAction required data path signature is defined in table 15-19 of SDM:
+-----------------------------------------------------------------------------+ | SRAR Error | Valid | OVER | UC | EN | MISCV | ADDRV | PCC | S | AR | MCACOD | | Data Load | 1 | 0 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 0x134 | +-----------------------------------------------------------------------------+
Recognise this, and pass MCE_AR_SEVERITY code back to do_machine_check()
--- arch/x86/kernel/cpu/mcheck/mce-severity.c | 14 +++++++++++++- 1 files changed, 13 insertions(+), 1 deletions(-)
arch/x86/kernel/cpu/mcheck/mce-severity.c +13 -1
@@ -54,6 +54,7 @@ static struct severity {#define MASK (x, y) .mask = x, .result = y#define MCI_UC_S (MCI_STATUS_UC|MCI_STATUS_S)#define MCI_UC_SAR (MCI_STATUS_UC|MCI_STATUS_S|MCI_STATUS_AR) +#define MCI_ADDR (MCI_STATUS_ADDRV|MCI_STATUS_MISCV)#define MCACOD 0xffff MCESEV(
@@ -102,11 +103,22 @@ static struct severity { SER, BITCLR(MCI_STATUS_S) ), -/* AR add known MCACODs here */ MCESEV (PANIC ,"Action required with lost events" ,SER ,BITSET (MCI_STATUS_OVER |MCI_UC_SAR ) ), + +/* known AR MCACODs: */ +MCESEV ( +KEEP ,"HT thread notices Action required: data load error" , +SER ,MASK (MCI_STATUS_OVER |MCI_UC_SAR |MCI_ADDR |MCACOD ,MCI_UC_SAR |MCI_ADDR |0x0134 ), +MCGMASK (MCG_STATUS_EIPV ,0 ) + ), +MCESEV ( +AR ,"Action required: data load error" , +SER ,MASK (MCI_STATUS_OVER |MCI_UC_SAR |MCI_ADDR |MCACOD ,MCI_UC_SAR |MCI_ADDR |0x0134 ), +USER + ),MCESEV (PANIC ,"Action required: unknown MCACOD" , SER, MASK(MCI_STATUS_OVER|MCI_UC_SAR, MCI_UC_SAR)
Signature · 1 line
1.7.3.1
PATCH 4/6 x86, mce: Add mechanism to safely save information in MCE handler
In reply to Tony LuckMachine checks on Intel cpus interrupt execution on all cpus, regardless of interrupt masking. We have a need to save some data about the cause of the machine check (physical address) in the machine check handler that can be retrieved later to attempt recovery in a more flexible execution state.
--- arch/x86/kernel/cpu/mcheck/mce.c | 43 ++++++++++++++++++++++++++++++++++++++ 1 files changed, 43 insertions(+), 0 deletions(-)
arch/x86/kernel/cpu/mcheck/mce.c +43 -0
@@ -887,6 +887,49 @@ static void mce_clear_state(unsigned long *toclear) }/* +* Need to save faulting physical address associated with a process +* in the machine check handler some place where we can grab it back +* later in mce_notify_process() +*/ +#define MAX_MCE_INFO 16 + +struct mce_info { +atomic_t inuse; +struct task_struct *t; +__u64 paddr; +} mce_info[MAX_MCE_INFO ]; + +static void mce_save_info (__u64 addr) +{ +struct mce_info *mi; + +for (mi = mce_info; mi < &mce_info[MAX_MCE_INFO ]; mi++) { +if (atomic_cmpxchg (&mi->inuse,0 ,1 ) ==0 ) { + mi->t = current; + mi->paddr = addr; +return ; + } + } + +mce_panic ("Too many concurrent recoverable errors" ,NULL ,NULL ); +} + +static struct mce_info *mce_find_info (void ) +{ +struct mce_info *mi; + +for (mi = mce_info; mi < &mce_info[MAX_MCE_INFO ]; mi++) +if (atomic_read (&mi->inuse) && mi->t == current) +return mi; +return NULL ; +} + +static void mce_clear_info (struct mce_info *mi) +{ +atomic_set (&mi->inuse,0 ); +} + +/* * The actual machine check handler. This only handles real * exceptions when something got corrupted coming in through int 18. *
Signature · 1 line
1.7.3.1
Re: [PATCH 4/6] x86, mce: Add mechanism to safely save information in MCE handler
arch/x86/kernel/cpu/mcheck/mce.c static void mce_clear_state(unsigned long *toclear) · line 894
Quoted 13 lines · Tony Luck
arch/x86/kernel/cpu/mcheck/mce.c +5
-0@@ -887,6 +887,49 @@ static void mce_clear_state(unsigned long *toclear) }/* +* Need to save faulting physical address associated with a process +* in the machine check handler some place where we can grab it back +* later in mce_notify_process() +*/ +#define MAX_MCE_INFO 16
(nitpick) IMHO, I'd prefer MCE_INFO_MAX.
Thanks,
H.Seto
Re: [PATCH 5/6] x86, mce: handle "action required" errors
In reply to Tony Luckarch/x86/kernel/cpu/mcheck/mce.c
Quoted 21 lines · Tony Luck
All non-urgent actions (reporting low severity errors and handling "action-optional" errors) are now handled by a work queue. This means that
TIF_MCE_NOTIFYcan be used to block execution for a thread experiencing an "action-required" fault until we get all cpus out of the machine check handler (and the thread that hit the fault intomce_notify_process().We use the new mce_{save,find,clear}_info() API to get information from
do_machine_check()tomce_notify_process(), and then use the newly improvedmemory_failure(..., MF_ACTION_REQUIRED)to handle the error (possibly signalling the process).Update some comments to make the new code flows clearer.
Signed-off-by Tony Luck <[email protected]>--- arch/x86/kernel/cpu/mcheck/mce.c | 70 ++++++++++++++++++++++++-------------- 1 files changed, 44 insertions(+), 26 deletions(-)arch/x86/kernel/cpu/mcheck/mce.c +0
-0
(snip)
... 2 patches in a mail?
Quoted 35 lines
--
1.7.3.1--- arch/x86/kernel/cpu/mcheck/mce.c | 71 ++++++++++++++++++++++++-------------- 1 files changed, 45 insertions(+), 26 deletions(-)arch/x86/kernel/cpu/mcheck/mce.c +3
-7@@ -982,7 +982,9 @@ void do_machine_check(struct pt_regs *regs, long error_code)barrier ();/* -* When no restart IP must always kill or panic. +* When no restart IP might need to kill or panic. +* Assume the worst for now, but if we find the +* severity is MCE_AR_SEVERITY we have other options. */ if (!(m.mcgstatus &MCG_STATUS_RIPV )) kill_it =1 ;@@ -1036,12 +1038,6 @@ void do_machine_check(struct pt_regs *regs, long error_code)continue ; } -/* -* Kill on action required. -*/ -if (severity ==MCE_AR_SEVERITY ) - kill_it =1 ; -mce_read_aux (&m, i);/*
arch/x86/kernel/cpu/mcheck/mce.c void do_machine_check(struct pt_regs *regs, long error_code) · line 1065
Quoted 8 lines
arch/x86/kernel/cpu/mcheck/mce.c +2
-0@@ -1062,6 +1058,8 @@ void do_machine_check(struct pt_regs *regs, long error_code) } } + m = *final; +if (!no_way_out)mce_clear_state (toclear);
Small change, but again, you should describe reason why...
Quoted 13 lines
arch/x86/kernel/cpu/mcheck/mce.c +1
-1@@ -1080,7 +1078,7 @@ void do_machine_check(struct pt_regs *regs, long error_code)* support MCE broadcasting or it has been disabled. */ if (no_way_out && tolerant <3 ) -mce_panic ("Fatal machine check on current CPU" , final, msg); +mce_panic ("Fatal machine check on current CPU" , &m, msg);/* * If the error seems to be unrecoverable, something should be @@ -1089,11 +1087,13 @@ void do_machine_check(struct pt_regs *regs, long error_code)* high, don't try to do anything at all. */
arch/x86/kernel/cpu/mcheck/mce.c void do_machine_check(struct pt_regs *regs, long error_code) · line 1096
Quoted 10 lines
arch/x86/kernel/cpu/mcheck/mce.c +5
-3-if (kill_it && tolerant <3 ) +if (worst !=MCE_AR_SEVERITY && kill_it && tolerant <3 )force_sig (SIGBUS , current); -/* notify userspace ASAP */ -set_thread_flag (TIF_MCE_NOTIFY ); +if (worst ==MCE_AR_SEVERITY ) { +mce_save_info (m.addr); +set_thread_flag (TIF_MCE_NOTIFY ); + }
I know tolerant==3 is an insane option, but it is better to care about it here too (or it would be happy if we can remove tolerant completely).
e.g.
if (tolerant < 3) {
if (no_way_out)
mce_panic(...);
if (worst == MCE_AR_SEVERITY) {
/* schedule action before return to userland */
mce_save_info(m.addr);
set_thread_flag(TIF_MCE_NOTIFY);
} else if (kill_it) {
force_sig(SIGBUS, current);
}
}Quoted 17 lines
arch/x86/kernel/cpu/mcheck/mce.c +2
-1if (worst >0 )mce_report_event (regs);@@ -1107,6 +1107,8 @@ EXPORT_SYMBOL_GPL(do_machine_check);#ifndef CONFIG_MEMORY_FAILURE int memory_failure (unsigned long pfn,int vector,int flags) { +if (flags &MF_ACTION_REQUIRED ) +return -ENXIO ;/* panic? */ printk (KERN_ERR "Uncorrected memory error in page 0x%lx ignored\n" "Rebuild kernel with CONFIG_MEMORY_FAILURE=y for smarter handling\n" , pfn);@@ -1115,27 +1117,46 @@ int memory_failure(unsigned long pfn, int vector, int flags)#endif /* -* Called after mce notification in process context. This code
arch/x86/kernel/cpu/mcheck/mce.c int memory_failure(unsigned long pfn, int vector, int flags) · line 1121
Quoted 10 lines
arch/x86/kernel/cpu/mcheck/mce.c +2
-8-* is allowed to sleep. Call the high level VM handler to process -* any corrupted pages. -* Assume that the work queue code only calls this one at a time -* per CPU. -* Note we don't disable preemption, so this code might run on the wrong -* CPU. In this case the event is picked up by the scheduled work queue. -* This is merely a fast path to expedite processing in some common -* cases. +* Called in process context that interrupted by MCE and marked with +* TIF_MCE_NOTFY, just before returning to errorneous userland.
Spell checker suggests: erroneous
Quoted 5 lines
arch/x86/kernel/cpu/mcheck/mce.c +4
-0+* This code is allowed to sleep. +* Attempt possible recovery such as calling the high level VM handler to +* process any corrupted pages, and kill/signal current process if required. +* Action required errors are handled here. */
arch/x86/kernel/cpu/mcheck/mce.c EXPORT_SYMBOL_GPL(do_machine_check); · line 1131
Quoted 10 lines
arch/x86/kernel/cpu/mcheck/mce.c +4
-3void mce_notify_process (void ) {unsigned long pfn; -mce_notify_irq (); -while (mce_ring_get (&pfn)) -memory_failure (pfn,MCE_VECTOR ,0 ); +struct mce_info *mi =mce_find_info (); + +if (!mi) +mce_panic ("Lost address" ,NULL ,NULL );
The message is too short, isn't it?
And if this case is an another version of "Memory error not recovered" located below then why not force_sig() but mce_panic()?
Quoted 31 lines
arch/x86/kernel/cpu/mcheck/mce.c +22
-1+ pfn = mi->paddr >>PAGE_SHIFT ; + +clear_thread_flag (TIF_MCE_NOTIFY ); + +pr_err ("Uncorrected hardware memory error in user-access at %llx" , + mi->paddr); +if (memory_failure (pfn,MCE_VECTOR ,MF_ACTION_REQUIRED ) <0 ) { +pr_err ("Memory error not recovered" ); +force_sig (SIGBUS , current); + }else { +pr_err ("Memory error recovered" ); + } +mce_clear_info (mi); } +/* +* Action optional processing happens here (picking up +* from the list of faulting pages that do_machine_check() +* placed into the "ring"). +*/ static void mce_process_work (struct work_struct *dummy) { -mce_notify_process (); +unsigned long pfn; + +while (mce_ring_get (&pfn)) +memory_failure (pfn,MCE_VECTOR ,0 ); }#ifdef CONFIG_X86_MCE_INTEL
arch/x86/kernel/cpu/mcheck/mce.c int mce_notify_irq(void) · line 1251
Quoted 8 lines
arch/x86/kernel/cpu/mcheck/mce.c +0
-2@@ -1225,8 +1246,6 @@ int mce_notify_irq(void)/* Not more than two messages every minute */ static DEFINE_RATELIMIT_STATE(ratelimit, 60*HZ, 2); -clear_thread_flag (TIF_MCE_NOTIFY ); -if (test_and_clear_bit (0 , &mce_need_notify)) {/* wake processes polling /dev/mcelog */ wake_up_interruptible (&mce_chrdev_wait);
Thanks,
H.Seto
Re: [PATCH 5/6] x86, mce: handle "action required" errors
2011/12/15 Hidetoshi Seto <[email protected]>:
Quoted 3 lines
(snip)
... 2 patches in a mail?
Sort of ... I pulled the old version of the patch into the commit editor - to just grab the description part, but I forgot to delete from "Signed-off-by" to end of file ... so the "extra" patch is now part of my commit comment, and the real patch starts further down.
Oops
-Tony
PATCH 5/6 x86, mce: handle "action required" errors (unjumbled version)
All non-urgent actions (reporting low severity errors and handling "action-optional" errors) are now handled by a work queue. This means that TIF_MCE_NOTIFY can be used to block execution for a thread experiencing an "action-required" fault until we get all cpus out of the machine check handler (and the thread that hit the fault into mce_notify_process().
We use the new mce_{save,find,clear}_info() API to get information from do_machine_check() to mce_notify_process(), and then use the newly improved memory_failure(..., MF_ACTION_REQUIRED) to handle the error (possibly signalling the process).
Update some comments to make the new code flows clearer.
---
[Version posted earlier had the diff included in the commit comment,
and then the real copy of the diff - making it hard to read. Sorry.]
arch/x86/kernel/cpu/mcheck/mce.c | 71 ++++++++++++++++++++++++-------------- 1 files changed, 45 insertions(+), 26 deletions(-)
arch/x86/kernel/cpu/mcheck/mce.c +45 -26
@@ -982,7 +982,9 @@ void do_machine_check(struct pt_regs *regs, long error_code)barrier ();/* -* When no restart IP must always kill or panic. +* When no restart IP might need to kill or panic. +* Assume the worst for now, but if we find the +* severity is MCE_AR_SEVERITY we have other options. */ if (!(m.mcgstatus &MCG_STATUS_RIPV )) kill_it =1 ;
@@ -1036,12 +1038,6 @@ void do_machine_check(struct pt_regs *regs, long error_code)continue ; } -/* -* Kill on action required. -*/ -if (severity ==MCE_AR_SEVERITY ) - kill_it =1 ; -mce_read_aux (&m, i);/*
@@ -1062,6 +1058,8 @@ void do_machine_check(struct pt_regs *regs, long error_code) } } + m = *final; +if (!no_way_out)mce_clear_state (toclear);
@@ -1080,7 +1078,7 @@ void do_machine_check(struct pt_regs *regs, long error_code)* support MCE broadcasting or it has been disabled. */ if (no_way_out && tolerant <3 ) -mce_panic ("Fatal machine check on current CPU" , final, msg); +mce_panic ("Fatal machine check on current CPU" , &m, msg);/* * If the error seems to be unrecoverable, something should be
@@ -1089,11 +1087,13 @@ void do_machine_check(struct pt_regs *regs, long error_code)* high, don't try to do anything at all. */ -if (kill_it && tolerant <3 ) +if (worst !=MCE_AR_SEVERITY && kill_it && tolerant <3 )force_sig (SIGBUS , current); -/* notify userspace ASAP */ -set_thread_flag (TIF_MCE_NOTIFY ); +if (worst ==MCE_AR_SEVERITY ) { +mce_save_info (m.addr); +set_thread_flag (TIF_MCE_NOTIFY ); + }if (worst >0 )mce_report_event (regs);
@@ -1107,6 +1107,8 @@ EXPORT_SYMBOL_GPL(do_machine_check);#ifndef CONFIG_MEMORY_FAILURE int memory_failure (unsigned long pfn,int vector,int flags) { +if (flags &MF_ACTION_REQUIRED ) +return -ENXIO ;/* panic? */ printk (KERN_ERR "Uncorrected memory error in page 0x%lx ignored\n" "Rebuild kernel with CONFIG_MEMORY_FAILURE=y for smarter handling\n" , pfn);
@@ -1115,27 +1117,46 @@ int memory_failure(unsigned long pfn, int vector, int flags)#endif /* -* Called after mce notification in process context. This code -* is allowed to sleep. Call the high level VM handler to process -* any corrupted pages. -* Assume that the work queue code only calls this one at a time -* per CPU. -* Note we don't disable preemption, so this code might run on the wrong -* CPU. In this case the event is picked up by the scheduled work queue. -* This is merely a fast path to expedite processing in some common -* cases. +* Called in process context that interrupted by MCE and marked with +* TIF_MCE_NOTFY, just before returning to errorneous userland. +* This code is allowed to sleep. +* Attempt possible recovery such as calling the high level VM handler to +* process any corrupted pages, and kill/signal current process if required. +* Action required errors are handled here. */ void mce_notify_process (void ) {unsigned long pfn; -mce_notify_irq (); -while (mce_ring_get (&pfn)) -memory_failure (pfn,MCE_VECTOR ,0 ); +struct mce_info *mi =mce_find_info (); + +if (!mi) +mce_panic ("Lost address" ,NULL ,NULL ); + pfn = mi->paddr >>PAGE_SHIFT ; + +clear_thread_flag (TIF_MCE_NOTIFY ); + +pr_err ("Uncorrected hardware memory error in user-access at %llx" , + mi->paddr); +if (memory_failure (pfn,MCE_VECTOR ,MF_ACTION_REQUIRED ) <0 ) { +pr_err ("Memory error not recovered" ); +force_sig (SIGBUS , current); + }else { +pr_err ("Memory error recovered" ); + } +mce_clear_info (mi); } +/* +* Action optional processing happens here (picking up +* from the list of faulting pages that do_machine_check() +* placed into the "ring"). +*/ static void mce_process_work (struct work_struct *dummy) { -mce_notify_process (); +unsigned long pfn; + +while (mce_ring_get (&pfn)) +memory_failure (pfn,MCE_VECTOR ,0 ); }#ifdef CONFIG_X86_MCE_INTEL
@@ -1225,8 +1246,6 @@ int mce_notify_irq(void)/* Not more than two messages every minute */ static DEFINE_RATELIMIT_STATE(ratelimit, 60*HZ, 2); -clear_thread_flag (TIF_MCE_NOTIFY ); -if (test_and_clear_bit (0 , &mce_need_notify)) {/* wake processes polling /dev/mcelog */ wake_up_interruptible (&mce_chrdev_wait);
Signature · 1 line
1.7.3.1
Re: [PATCH 5/6] x86, mce: handle "action required" errors
In reply to Hidetoshi Seto2011/12/15 Hidetoshi Seto <[email protected]>:
Quoted 7 lines
Quoted 5 lines
+ m = *final;
+
if (!no_way_out)
mce_clear_state(toclear);Small change, but again, you should describe reason why...
Yes - this is subtle (mce_clear_state() will clear what *final points to, so make a copy in the local variable "m"). It deserves a comment, so I'll add one.
Quoted 15 lines
I know tolerant==3 is an insane option, but it is better to care about it here too (or it would be happy if we can remove tolerant completely).
e.g.
if (tolerant < 3) {
if (no_way_out)
mce_panic(...);
if (worst ==MCE_AR_SEVERITY) {
/* schedule action before return to userland */mce_save_info(m.addr);set_thread_flag(TIF_MCE_NOTIFY);
} else if (kill_it) {
force_sig(SIGBUS, current);
}
}
Good point. But I don't see how "tolerant==3" and "AR" errors ever make sense together. If we don't do something to fix the problem and just ignore it, then we
will take a new machine check when we re-execute the instruction (unless the problem magically went away ... but I don't think that is likely). So the a user with tolerant=3 will loop taking the same machine check over and over. Which isn't likely to be what was wanted.
Quoted 3 lines
Quoted 1 line
+ *
TIF_MCE_NOTFY, just before returning to errorneous userland.Spell checker suggests: erroneous
Will fix.
Quoted 4 lines
Quoted 2 lines
+ if (!mi)
+mce_panic("Lost address", NULL, NULL);The message is too short, isn't it?
Yes - it's a "Can't happen" error case (if we are here, then we must have saved the address when we set TIF_MCE_NOTIFY - so the only way to not find the address is for someone else to have corrupted out mce_info[] array). Perhaps I should change to BUG_ON()?
Quoted 2 lines
And if this case is an another version of "Memory error not recovered" located below then why not
force_sig()butmce_panic()?
The more I look at that "Memory error not recovered" code, the more I think that it should be a panic (almost the same logic as for tolerant=3, in this case force_sig would prevent us from running right back into the machine check - but we did nothing to poison the page
Thanks for looking at this.
-Tony
Re: [PATCH 4/6] x86, mce: Add mechanism to safely save information in MCE handler
In reply to Tony LuckQuoted 26 lines · Tony Luck
Machine checks on Intel cpus interrupt execution on all cpus, regardless of interrupt masking. We have a need to save some data about the cause of the machine check (physical address) in the machine check handler that can be retrieved later to attempt recovery in a more flexible execution state.
Signed-off-by Tony Luck <[email protected]>--- arch/x86/kernel/cpu/mcheck/mce.c | 43 ++++++++++++++++++++++++++++++++++++++ 1 files changed, 43 insertions(+), 0 deletions(-)arch/x86/kernel/cpu/mcheck/mce.c +7
-0@@ -887,6 +887,49 @@ static void mce_clear_state(unsigned long *toclear) }/* +* Need to save faulting physical address associated with a process +* in the machine check handler some place where we can grab it back +* later in mce_notify_process() +*/ +#define MAX_MCE_INFO 16 + +struct mce_info {
arch/x86/kernel/cpu/mcheck/mce.c static void mce_clear_state(unsigned long *toclear) · line 906
Quoted 10 lines
arch/x86/kernel/cpu/mcheck/mce.c +10
-0+atomic_t inuse; +struct task_struct *t; +__u64 paddr; +} mce_info[MAX_MCE_INFO ]; + +static void mce_save_info (__u64 addr) +{ +struct mce_info *mi; + +for (mi = mce_info; mi < &mce_info[MAX_MCE_INFO ]; mi++) {
This looks strange, although valid. I thought we do
for (i = 0; i < MCE_INFO_MAX; i++) {
struct mce_info *mi = &mce_info[i];
...in such loops. Just a nitpick I guess.
arch/x86/kernel/cpu/mcheck/mce.c static void mce_clear_state(unsigned long *toclear) · line 914
Quoted 8 lines
arch/x86/kernel/cpu/mcheck/mce.c +8
-0+if (atomic_cmpxchg (&mi->inuse,0 ,1 ) ==0 ) { + mi->t = current; + mi->paddr = addr; +return ; + } + } + +mce_panic ("Too many concurrent recoverable errors" ,NULL ,NULL );
So we're setting an artificial limit of 16 in-flight AR errors and if > 16, we're panicking? Do we really want to do that? I guess we do... I got nothing better anyway.
Thanks.
Signature · 8 lines
Regards/Gruss, Boris. Advanced Micro Devices GmbH Einsteinring 24, 85609 Dornach GM: Alberto Bozzo Reg: Dornach, Landkreis Muenchen HRB Nr. 43632 WEEE Registernr: 129 19551
Re: [PATCH 1/6] HWPOISON: clean up memory_failure() vs. __memory_failure()
In reply to Tony LuckQuoted 10 lines · Tony Luck
There is only one caller of
memory_failure(), all other users call__memory_failure()and pass in the flags argument explicitly. The lone user ofmemory_failure()will soon need to pass flags too.Add flags argument to the callsite in
mce.c. Delete the oldmemory_failure()function, and then rename__memory_failure()without the leading "__".Provide clearer message when action optional memory errors are ignored.
Signed-off-by Tony Luck <[email protected]>
ACK.
Thanks.
Signature · 8 lines
Regards/Gruss, Boris. Advanced Micro Devices GmbH Einsteinring 24, 85609 Dornach GM: Alberto Bozzo Reg: Dornach, Landkreis Muenchen HRB Nr. 43632 WEEE Registernr: 129 19551
Re: [PATCH 5/6] x86, mce: handle "action required" errors (unjumbled version)
In reply to Tony LuckQuoted 87 lines · Tony Luck
All non-urgent actions (reporting low severity errors and handling "action-optional" errors) are now handled by a work queue. This means that
TIF_MCE_NOTIFYcan be used to block execution for a thread experiencing an "action-required" fault until we get all cpus out of the machine check handler (and the thread that hit the fault intomce_notify_process().We use the new mce_{save,find,clear}_info() API to get information from
do_machine_check()tomce_notify_process(), and then use the newly improvedmemory_failure(..., MF_ACTION_REQUIRED)to handle the error (possibly signalling the process).Update some comments to make the new code flows clearer.
Signed-off-by Tony Luck <[email protected]>---
[Version posted earlier had the diff included in the commit comment,
and then the real copy of the diff - making it hard to read. Sorry.]arch/x86/kernel/cpu/mcheck/mce.c | 71 ++++++++++++++++++++++++-------------- 1 files changed, 45 insertions(+), 26 deletions(-)arch/x86/kernel/cpu/mcheck/mce.c +11
-11@@ -982,7 +982,9 @@ void do_machine_check(struct pt_regs *regs, long error_code)barrier ();/* -* When no restart IP must always kill or panic. +* When no restart IP might need to kill or panic. +* Assume the worst for now, but if we find the +* severity is MCE_AR_SEVERITY we have other options. */ if (!(m.mcgstatus &MCG_STATUS_RIPV )) kill_it =1 ;@@ -1036,12 +1038,6 @@ void do_machine_check(struct pt_regs *regs, long error_code)continue ; } -/* -* Kill on action required. -*/ -if (severity ==MCE_AR_SEVERITY ) - kill_it =1 ; -mce_read_aux (&m, i);/* @@ -1062,6 +1058,8 @@ void do_machine_check(struct pt_regs *regs, long error_code) } } + m = *final; +if (!no_way_out)mce_clear_state (toclear);@@ -1080,7 +1078,7 @@ void do_machine_check(struct pt_regs *regs, long error_code)* support MCE broadcasting or it has been disabled. */ if (no_way_out && tolerant <3 ) -mce_panic ("Fatal machine check on current CPU" , final, msg); +mce_panic ("Fatal machine check on current CPU" , &m, msg);/* * If the error seems to be unrecoverable, something should be @@ -1089,11 +1087,13 @@ void do_machine_check(struct pt_regs *regs, long error_code)* high, don't try to do anything at all. */ -if (kill_it && tolerant <3 ) +if (worst !=MCE_AR_SEVERITY && kill_it && tolerant <3 )force_sig (SIGBUS , current); -/* notify userspace ASAP */ -set_thread_flag (TIF_MCE_NOTIFY ); +if (worst ==MCE_AR_SEVERITY ) { +mce_save_info (m.addr); +set_thread_flag (TIF_MCE_NOTIFY ); + }if (worst >0 )mce_report_event (regs);
arch/x86/kernel/cpu/mcheck/mce.c EXPORT_SYMBOL_GPL(do_machine_check); · line 1111
Quoted 5 lines
arch/x86/kernel/cpu/mcheck/mce.c +2
-0@@ -1107,6 +1107,8 @@ EXPORT_SYMBOL_GPL(do_machine_check);#ifndef CONFIG_MEMORY_FAILURE int memory_failure (unsigned long pfn,int vector,int flags) { +if (flags &MF_ACTION_REQUIRED ) +return -ENXIO ;/* panic? */
Yes, an AR error _is_ an uncorrectable error so in order to stay backwards-compatible, we should panic here unconditionally IMO.
Quoted 8 lines
arch/x86/kernel/cpu/mcheck/mce.c +0
-1printk (KERN_ERR "Uncorrected memory error in page 0x%lx ignored\n" "Rebuild kernel with CONFIG_MEMORY_FAILURE=y for smarter handling\n" , pfn);@@ -1115,27 +1117,46 @@ int memory_failure(unsigned long pfn, int vector, int flags)#endif /* -* Called after mce notification in process context. This code
arch/x86/kernel/cpu/mcheck/mce.c int memory_failure(unsigned long pfn, int vector, int flags) · line 1121
Quoted 10 lines
arch/x86/kernel/cpu/mcheck/mce.c +2
-8-* is allowed to sleep. Call the high level VM handler to process -* any corrupted pages. -* Assume that the work queue code only calls this one at a time -* per CPU. -* Note we don't disable preemption, so this code might run on the wrong -* CPU. In this case the event is picked up by the scheduled work queue. -* This is merely a fast path to expedite processing in some common -* cases. +* Called in process context that interrupted by MCE and marked with +* TIF_MCE_NOTFY, just before returning to errorneous userland.
TIF_MCE_NOTIFY
Quoted 5 lines
arch/x86/kernel/cpu/mcheck/mce.c +4
-0+* This code is allowed to sleep. +* Attempt possible recovery such as calling the high level VM handler to +* process any corrupted pages, and kill/signal current process if required. +* Action required errors are handled here. */
arch/x86/kernel/cpu/mcheck/mce.c int memory_failure(unsigned long pfn, int vector, int flags) · line 1133
Quoted 10 lines
arch/x86/kernel/cpu/mcheck/mce.c +4
-3void mce_notify_process (void ) {unsigned long pfn; -mce_notify_irq (); -while (mce_ring_get (&pfn)) -memory_failure (pfn,MCE_VECTOR ,0 ); +struct mce_info *mi =mce_find_info (); + +if (!mi) +mce_panic ("Lost address" ,NULL ,NULL );
Yeah, maybe "Lost physical address for unconsumed uncorrectable error"
arch/x86/kernel/cpu/mcheck/mce.c int memory_failure(unsigned long pfn, int vector, int flags) · line 1144
Quoted 11 lines
arch/x86/kernel/cpu/mcheck/mce.c +11
-0+ pfn = mi->paddr >>PAGE_SHIFT ; + +clear_thread_flag (TIF_MCE_NOTIFY ); + +pr_err ("Uncorrected hardware memory error in user-access at %llx" , + mi->paddr); +if (memory_failure (pfn,MCE_VECTOR ,MF_ACTION_REQUIRED ) <0 ) { +pr_err ("Memory error not recovered" ); +force_sig (SIGBUS , current); + }else { +pr_err ("Memory error recovered" );
No need for that because memory_failure() is chatty enough already, due to action_result()?
Quoted 21 lines
arch/x86/kernel/cpu/mcheck/mce.c +11
-1+ } +mce_clear_info (mi); } +/* +* Action optional processing happens here (picking up +* from the list of faulting pages that do_machine_check() +* placed into the "ring"). +*/ static void mce_process_work (struct work_struct *dummy) { -mce_notify_process (); +unsigned long pfn; + +while (mce_ring_get (&pfn)) +memory_failure (pfn,MCE_VECTOR ,0 ); }#ifdef CONFIG_X86_MCE_INTEL
arch/x86/kernel/cpu/mcheck/mce.c int mce_notify_irq(void) · line 1251
Quoted 8 lines
arch/x86/kernel/cpu/mcheck/mce.c +0
-2@@ -1225,8 +1246,6 @@ int mce_notify_irq(void)/* Not more than two messages every minute */ static DEFINE_RATELIMIT_STATE(ratelimit, 60*HZ, 2); -clear_thread_flag (TIF_MCE_NOTIFY ); -if (test_and_clear_bit (0 , &mce_need_notify)) {/* wake processes polling /dev/mcelog */ wake_up_interruptible (&mce_chrdev_wait);
Thanks.
Signature · 8 lines
Regards/Gruss, Boris. Advanced Micro Devices GmbH Einsteinring 24, 85609 Dornach GM: Alberto Bozzo Reg: Dornach, Landkreis Muenchen HRB Nr. 43632 WEEE Registernr: 129 19551
PATCH 5/6 x86, mce: handle "action required" errors (new version)
In reply to Tony LuckAll non-urgent actions (reporting low severity errors and handling "action-optional" errors) are now handled by a work queue. This means that TIF_MCE_NOTIFY can be used to block execution for a thread experiencing an "action-required" fault until we get all cpus out of the machine check handler (and the thread that hit the fault into mce_notify_process().
We use the new mce_{save,find,clear}_info() API to get information from do_machine_check() to mce_notify_process(), and then use the newly improved memory_failure(..., MF_ACTION_REQUIRED) to handle the error (possibly signalling the process).
Update some comments to make the new code flows clearer.
---
Included spelling fixes from Boris & Seto-san ... but the big change here from last version is re-arranging the action code as suggested by Seto-san ... to be suitably insane if "tolerant" is set to 3. This makes the code a little easier to read - merged and updated the comments above this section to keep up with the code changes.
In the final stretch? ... in case it makes things easier for anyone to look at this, I pushed the current set of patches to:
git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git mce-recovery-test
arch/x86/kernel/cpu/mcheck/mce.c | 97 +++++++++++++++++++++---------------- 1 files changed, 55 insertions(+), 42 deletions(-)
arch/x86/kernel/cpu/mcheck/mce.c +55 -42
@@ -982,7 +982,9 @@ void do_machine_check(struct pt_regs *regs, long error_code)barrier ();/* -* When no restart IP must always kill or panic. +* When no restart IP might need to kill or panic. +* Assume the worst for now, but if we find the +* severity is MCE_AR_SEVERITY we have other options. */ if (!(m.mcgstatus &MCG_STATUS_RIPV )) kill_it =1 ;
@@ -1036,12 +1038,6 @@ void do_machine_check(struct pt_regs *regs, long error_code)continue ; } -/* -* Kill on action required. -*/ -if (severity ==MCE_AR_SEVERITY ) - kill_it =1 ; -mce_read_aux (&m, i);/*
@@ -1062,6 +1058,9 @@ void do_machine_check(struct pt_regs *regs, long error_code) } } +/* mce_clear_state will clear *final, save locally for use later */ + m = *final; +if (!no_way_out)mce_clear_state (toclear);
@@ -1073,27 +1072,22 @@ void do_machine_check(struct pt_regs *regs, long error_code) no_way_out = worst >=MCE_PANIC_SEVERITY ;/* -* If we have decided that we just CAN'T continue, and the user -* has not set tolerant to an insane level, give up and die. -* -* This is mainly used in the case when the system doesn't -* support MCE broadcasting or it has been disabled. +* At insane "tolerant" levels we take no action. Otherwise +* we only die if we have no other choice. For less serious +* issues we try to recover, or limit damage to the current +* process. */ -if (no_way_out && tolerant <3 ) -mce_panic ("Fatal machine check on current CPU" , final, msg); - -/* -* If the error seems to be unrecoverable, something should be -* done. Try to kill as little as possible. If we can kill just -* one task, do that. If the user has set the tolerance very -* high, don't try to do anything at all. -*/ - -if (kill_it && tolerant <3 ) -force_sig (SIGBUS , current); - -/* notify userspace ASAP */ -set_thread_flag (TIF_MCE_NOTIFY ); +if (tolerant <3 ) { +if (no_way_out) +mce_panic ("Fatal machine check on current CPU" , &m, msg); +if (worst ==MCE_AR_SEVERITY ) { +/* schedule action before return to userland */ +mce_save_info (m.addr); +set_thread_flag (TIF_MCE_NOTIFY ); + }else if (kill_it) { +force_sig (SIGBUS , current); + } + }if (worst >0 )mce_report_event (regs);
@@ -1107,6 +1101,8 @@ EXPORT_SYMBOL_GPL(do_machine_check);#ifndef CONFIG_MEMORY_FAILURE int memory_failure (unsigned long pfn,int vector,int flags) { +if (flags &MF_ACTION_REQUIRED ) +return -ENXIO ;/* panic? */ printk (KERN_ERR "Uncorrected memory error in page 0x%lx ignored\n" "Rebuild kernel with CONFIG_MEMORY_FAILURE=y for smarter handling\n" , pfn);
@@ -1115,27 +1111,46 @@ int memory_failure(unsigned long pfn, int vector, int flags)#endif /* -* Called after mce notification in process context. This code -* is allowed to sleep. Call the high level VM handler to process -* any corrupted pages. -* Assume that the work queue code only calls this one at a time -* per CPU. -* Note we don't disable preemption, so this code might run on the wrong -* CPU. In this case the event is picked up by the scheduled work queue. -* This is merely a fast path to expedite processing in some common -* cases. +* Called in process context that interrupted by MCE and marked with +* TIF_MCE_NOTIFY, just before returning to erroneous userland. +* This code is allowed to sleep. +* Attempt possible recovery such as calling the high level VM handler to +* process any corrupted pages, and kill/signal current process if required. +* Action required errors are handled here. */ void mce_notify_process (void ) {unsigned long pfn; -mce_notify_irq (); -while (mce_ring_get (&pfn)) -memory_failure (pfn,MCE_VECTOR ,0 ); +struct mce_info *mi =mce_find_info (); + +if (!mi) +mce_panic ("Lost physical address for unconsumed uncorrectable error" ,NULL ,NULL ); + pfn = mi->paddr >>PAGE_SHIFT ; + +clear_thread_flag (TIF_MCE_NOTIFY ); + +pr_err ("Uncorrected hardware memory error in user-access at %llx" , + mi->paddr); +if (memory_failure (pfn,MCE_VECTOR ,MF_ACTION_REQUIRED ) <0 ) { +pr_err ("Memory error not recovered" ); +force_sig (SIGBUS , current); + }else { +pr_err ("Memory error recovered" ); + } +mce_clear_info (mi); } +/* +* Action optional processing happens here (picking up +* from the list of faulting pages that do_machine_check() +* placed into the "ring"). +*/ static void mce_process_work (struct work_struct *dummy) { -mce_notify_process (); +unsigned long pfn; + +while (mce_ring_get (&pfn)) +memory_failure (pfn,MCE_VECTOR ,0 ); }#ifdef CONFIG_X86_MCE_INTEL
@@ -1225,8 +1240,6 @@ int mce_notify_irq(void)/* Not more than two messages every minute */ static DEFINE_RATELIMIT_STATE(ratelimit, 60*HZ, 2); -clear_thread_flag (TIF_MCE_NOTIFY ); -if (test_and_clear_bit (0 , &mce_need_notify)) {/* wake processes polling /dev/mcelog */ wake_up_interruptible (&mce_chrdev_wait);
Signature · 1 line
1.7.3.1
Re: [PATCH 5/6] x86, mce: handle "action required" errors (unjumbled version)
In reply to Borislav PetkovQuoted 8 lines · Borislav Petkov
Quoted 5 lines
#ifndef
CONFIG_MEMORY_FAILURE
intmemory_failure(unsigned long pfn, int vector, int flags){
+ if (flags &MF_ACTION_REQUIRED)
+ return-ENXIO; /* panic? */Yes, an AR error _is_ an uncorrectable error so in order to stay backwards-compatible, we should panic here unconditionally IMO.
I just thought of a better way ... I'll change part 6 of this patch set to put the severity recognition entries for "AR" errors inside of #ifdef CONFIG_MEMORY_FAILURE. It makes no sense to mark these
as action required severity if we don't have the code configured that can take the action. It makes more sense for the severity analysis to just flag them as "PANIC" events (which the catch-all AR=1 case in the severity table will do without the MCACOD=0x134 entries).
Then I can simplify here ... perhaps put:
BUG_ON(flags & MF_ACTION_REQUIRED);
here so if a future change to the severity parser does let an action required error slip through, we'll be able to see that was the problem was in the severity analysis.
-Tony