1. 20 Oct, 2021 1 commit
  2. 18 Oct, 2021 1 commit
  3. 24 Sep, 2021 1 commit
  4. 21 Sep, 2021 2 commits
  5. 06 Sep, 2021 7 commits
  6. 02 Sep, 2021 1 commit
  7. 31 Aug, 2021 5 commits
  8. 30 Aug, 2021 2 commits
    • Daniel Agar's avatar
    • Jukka Laitinen's avatar
      Fix memory corruption when work queue is being deleted · d1c09ec3
      Jukka Laitinen authored
      
      
      When the last WorkItem is deleted, it is removed from a work queue and the
      queue is being stopped. But, the queue itself might get deleted in the middle,
      in a higher priority thread than where the WorkItem deletion was performed from
      
      If the WorkQueue::Detach accesses the member variables after this, there is memory
      corruption
      
      This happens in particular when launching i2c or spi devices in
      I2CSPIDriverBase::module_start:
      
      - The "initializer" is deleted when the instance is not found and the iterator
        while loop continues.
      - The workqueue is deleted in the middle of "initializer" deletion when the
        WorkQueueRunner returns.
      
      This prevents deletion of the WorkQueue before the Detach has been finished,
      in the specific case that the ::Detach triggers the deletion
      Signed-off-by: default avatarJukka Laitinen <jukkax@ssrc.tii.ae>
      d1c09ec3
  9. 27 Aug, 2021 2 commits
  10. 23 Aug, 2021 1 commit
  11. 21 Aug, 2021 10 commits
  12. 12 Aug, 2021 2 commits
  13. 02 Aug, 2021 1 commit
  14. 01 Aug, 2021 3 commits
  15. 27 Jul, 2021 1 commit