Re: [PATCH] seqlock: fix seqlock_write_unlock_impl function

2020-01-29 Thread Paolo Bonzini
On 29/01/20 15:49, Luc Michel wrote: > The seqlock write unlock function was incorrectly calling > seqlock_write_begin() instead of seqlock_write_end(), and was releasing > the lock before incrementing the sequence. This could lead to a race > condition and a corrupted sequence number becoming odd

Re: [PATCH] seqlock: fix seqlock_write_unlock_impl function

2020-01-29 Thread Philippe Mathieu-Daudé
On 1/29/20 3:49 PM, Luc Michel wrote: The seqlock write unlock function was incorrectly calling seqlock_write_begin() instead of seqlock_write_end(), and was releasing the lock before incrementing the sequence. This could lead to a race condition and a corrupted sequence number becoming odd even

[PATCH] seqlock: fix seqlock_write_unlock_impl function

2020-01-29 Thread Luc Michel
The seqlock write unlock function was incorrectly calling seqlock_write_begin() instead of seqlock_write_end(), and was releasing the lock before incrementing the sequence. This could lead to a race condition and a corrupted sequence number becoming odd even though the lock is not held. Signed-off