On Mon, 04 Apr 2016, Michal Hocko wrote:
Not sure I got your point here.
You set current to TASK_KILLABLE in the sleep loop, why do you want to change it here to TASK_RUNNING if its about to be killed? At least in the case of UNINTERRUPTABLE we do it merely as a redundancy after the breaking out of the loop. Of course we also acquired the lock in the first place by that time and we _better_ be running. Thanks, Davidlohr -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
