Am 25.10.18 um 09:51 schrieb Maarten Lankhorst:
Op 25-10-18 om 08:53 schreef Christian KÃnig:Another possibility would to not allocate the dummy fence at all.
Am 25.10.18 um 03:28 schrieb Zhou, David(ChunMing):Yeah +1. Especially in a case like this where it's obvious to prevent. :)
Reviewed-by: Chunming Zhou <david1.zhou@xxxxxxx>NAK, GFP_ATOMIC should be avoided.
The correct solution is to move the allocation out of the spinlock or drop the lock and reacquire.
E.g. we just need a global instance of that which is always signaled and
has a reference count of +1.