Hello! We are using linux-2.4.32 We are now testing of cluster system configured by lifekeeper. When we linkdown FC disks, lifekeeper detected the error and called reboot(2) two or more times at the same time. In sys_reboot() function, lock_kernel() was called, but some drivers(ex. megaraid2 driver) called by notifier_call_chain() (When it is megaraid2 driver, it is megaraid_reboot_notify()) calls schedule() or schedule_timeout() in thefunction and it cause the destruction of kernel lock. As a result, dead lock occures in the notifier function of the driver and system hang occurred. What do you think which is better to keep lock? 1.lock in the sys_reboot() and each drivers called by notifier_call_chain() should not break the lock(not to call schedule() or schedule_timeout() function). 2.each drivers called by notifier_call_chain(U) mentions lock in their functions each other. I am not on this mailing list, please cc to me. to : minemoto@xxxxxxxxxxxxxxxx Best regards, shintaro minemoto - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
