diff options
| author | Andrew Vagin <avagin@openvz.org> | 2012-03-07 05:49:56 -0500 |
|---|---|---|
| committer | Luis Henriques <luis.henriques@canonical.com> | 2012-04-05 11:17:22 -0400 |
| commit | d95f912470daf6bdbe51b30f4c782a2a2de6a486 (patch) | |
| tree | 6bd1e576ea9d3d326b4f7c697d6f09c8be8b36a1 /kernel/irq/manage.c | |
| parent | 65fe18ee7b4a313630a32ac7d121703c63efb634 (diff) | |
uevent: send events in correct order according to seqnum (v3)
BugLink: http://bugs.launchpad.net/bugs/971808
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 'kernel/irq/manage.c')
0 files changed, 0 insertions, 0 deletions