Does anybody know for sure whether scsi_alloc_sdev() is guaranteed to be called in process context or not? There seem to be contradictory signs in scsi_scan.c: scsi_alloc_sdev() uses GFP_ATOMIC, as related functions do. It might be called in a section protected by a mutex. I conducted a little experiment using might_sleep() in scsi_alloc_sdev() - no backtrace on the console, hence process context. Or, is the purpose of GFP_ATOMIC just (SCSI) I/O avoidance, and sleeping isn't an issue? Thanks, Martin - : 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
