[PATCH] ipmi: fix watchdog so the device can be reopened on an unexpected close
If there is an unexpected close, still allow the watchdog interface to be re-opened on the IPMI watchdog. Signed-off-by: Corey Minyard <minyard@acm.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
This commit is contained in:
parent
35bc37a0e0
commit
ec26d79f4f
@ -709,11 +709,11 @@ static int ipmi_close(struct inode *ino, struct file *filep)
|
|||||||
if (expect_close == 42) {
|
if (expect_close == 42) {
|
||||||
ipmi_watchdog_state = WDOG_TIMEOUT_NONE;
|
ipmi_watchdog_state = WDOG_TIMEOUT_NONE;
|
||||||
ipmi_set_timeout(IPMI_SET_TIMEOUT_NO_HB);
|
ipmi_set_timeout(IPMI_SET_TIMEOUT_NO_HB);
|
||||||
clear_bit(0, &ipmi_wdog_open);
|
|
||||||
} else {
|
} else {
|
||||||
printk(KERN_CRIT PFX "Unexpected close, not stopping watchdog!\n");
|
printk(KERN_CRIT PFX "Unexpected close, not stopping watchdog!\n");
|
||||||
ipmi_heartbeat();
|
ipmi_heartbeat();
|
||||||
}
|
}
|
||||||
|
clear_bit(0, &ipmi_wdog_open);
|
||||||
}
|
}
|
||||||
|
|
||||||
ipmi_fasync (-1, filep, 0);
|
ipmi_fasync (-1, filep, 0);
|
||||||
|
Loading…
Reference in New Issue
Block a user