diff options
| author | Andrew Vagin <avagin@openvz.org> | 2012-03-07 14:49:56 +0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-04-02 09:27:09 -0700 |
| commit | 377c2f4aa985f937d77a6bb9b938b4deda2dc282 (patch) | |
| tree | eda5f5a602c6072e5d083d0c794401b9c55b5db3 /tools/perf/builtin-buildid-cache.c | |
| parent | d16d493a1c1079e4e065ee6070b2413add846719 (diff) | |
| download | kernel_samsung_smdk4412-377c2f4aa985f937d77a6bb9b938b4deda2dc282.tar.gz kernel_samsung_smdk4412-377c2f4aa985f937d77a6bb9b938b4deda2dc282.tar.bz2 kernel_samsung_smdk4412-377c2f4aa985f937d77a6bb9b938b4deda2dc282.zip | |
uevent: send events in correct order according to seqnum (v3)
commit 7b60a18da393ed70db043a777fd9e6d5363077c4 upstream.
The queue handling in the udev daemon assumes that the events are
ordered.
Before this patch uevent_seqnum is incremented under sequence_lock,
than an event is send uner uevent_sock_mutex. I want to say that code
contained a window between incrementing seqnum and sending an event.
This patch locks uevent_sock_mutex before incrementing uevent_seqnum.
v2: delete sequence_lock, uevent_seqnum is protected by uevent_sock_mutex
v3: unlock the mutex before the goto exit
Thanks for Kay for the comments.
Signed-off-by: Andrew Vagin <avagin@openvz.org>
Tested-By: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/builtin-buildid-cache.c')
0 files changed, 0 insertions, 0 deletions