aboutsummaryrefslogtreecommitdiffstats
path: root/arch/s390/kernel/crash_dump.c
diff options
context:
space:
mode:
authorAndrew Vagin <avagin@openvz.org>2012-03-07 14:49:56 +0400
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-03-08 12:56:40 -0800
commit7b60a18da393ed70db043a777fd9e6d5363077c4 (patch)
treecf83f1b5fdd5b7fab96c256f40db877112b277fe /arch/s390/kernel/crash_dump.c
parentdriver core: minor comment formatting cleanups (diff)
downloadlinux-dev-7b60a18da393ed70db043a777fd9e6d5363077c4.tar.xz
linux-dev-7b60a18da393ed70db043a777fd9e6d5363077c4.zip
uevent: send events in correct order according to seqnum (v3)
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> Cc: stable <stable@vger.kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch/s390/kernel/crash_dump.c')
0 files changed, 0 insertions, 0 deletions