{"push_id":3171888278,"size":2,"distinct_size":2,"ref":"refs/heads/pr/20181230a","head":"c8a9da77823424d45eb4801b7eeb75f9ef95d356","before":"d51f9a1436fae861cfba6c017f83713d2e707f0c","commits":[{"sha":"cd6a6c63a07422cf08b75da77bf48698cc44b9d1","author":{"name":"Peter A. Bigot","email":"650538893330be855f76604594b4820eb226769e@pabigot.com"},"message":"kernel: timeout: fix \"not in list\" predication in timeout handling\n\nIssue description by Andy Ross:\n\nThe use of dticks == INACTIVE to tell whether or not a timeout was\nalready in the list was insufficient.  There is a time period between\nthe moment a timeout is removed from the list and the end of its handler\nwhere it is not in the list, yet its list node pointers still point into\nit.  Doing things like aborting a thread while that is true (which can\nbe asynchronous too!) would corrupt the list even though all the\noperations on it were \"atomic\".\n\nUse a double-remove check that doesn't depend on a secondary indicator.\n\nSigned-off-by: Peter A. Bigot <pab@pabigot.com>","distinct":true,"url":"https://api.github.com/repos/pabigot/zephyr/commits/cd6a6c63a07422cf08b75da77bf48698cc44b9d1"},{"sha":"c8a9da77823424d45eb4801b7eeb75f9ef95d356","author":{"name":"Peter A. Bigot","email":"650538893330be855f76604594b4820eb226769e@pabigot.com"},"message":"kernel: poll: fix double-remove of node\n\nk_poll events are registered in a linked list when their signal\ncondition has been met.  The code to clear event registration did not\naccount for events that were not registered, resulting in double-removes\nthat produced core dumps on native-posix sanitycheck.\n\nSigned-off-by: Peter A. Bigot <pab@pabigot.com>","distinct":true,"url":"https://api.github.com/repos/pabigot/zephyr/commits/c8a9da77823424d45eb4801b7eeb75f9ef95d356"}]}
{"actor":{"display_login":"pabigot"}}