From: Saeed Mahameed
Date: Wed, 24 Feb 2016 13:18:49 +0200
> From: Eran Ben Elisha
>
> Readers/Writers lock for SW timecounter was acquired without disabling
> interrupts on local CPU.
>
> The problematic scenario:
> * HW timestamping is enabled
> * Timestamp overflow periodic service task is
From: Eran Ben Elisha
Readers/Writers lock for SW timecounter was acquired without disabling
interrupts on local CPU.
The problematic scenario:
* HW timestamping is enabled
* Timestamp overflow periodic service task is running on local CPU and
holding write_lock for SW timecounter
* Completion