>>> Does the existing memory allocation error message include the >>> &udev->dev device name and driver name? If it doesn't, there will be >>> no way for the user to tell that the error message is related to the >>> device failure. >> >> No, but the effect is similar. >> >> OOM does a dump_stack() so this function's call tree is shown. > > A call stack doesn't tell you which device was being handled.
Do you find a default Linux allocation failure report insufficient then? Would you like to to achieve that the requested information can be determined from a backtrace? Regards, Markus -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
