Revision 6cf11ee6300f38b7cfc43af9b7be2afaa5e05869 authored by Hans Verkuil on 19 January 2015, 09:16:18 UTC, committed by Mauro Carvalho Chehab on 21 January 2015, 23:07:26 UTC
The locking scheme inside the vb2 thread is unsafe when stopping the thread. In particular kthread_stop was called *after* internal data structures were cleaned up instead of doing that before. In addition, internal vb2 functions were called after threadio->stop was set to true and vb2_internal_streamoff was called. This is also not allowed. All this led to a variety of race conditions and kernel warnings and/or oopses. Fixed by moving the kthread_stop call up before the cleanup takes place, and by checking threadio->stop before calling internal vb2 queuing operations. Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com> Cc: <stable@vger.kernel.org> # for v3.16 and up Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
1 parent 42d74e4
File | Mode | Size |
---|---|---|
Kconfig | -rw-r--r-- | 1.6 KB |
Makefile | -rw-r--r-- | 180 bytes |
config.c | -rw-r--r-- | 300 bytes |
virtio.c | -rw-r--r-- | 9.0 KB |
virtio_balloon.c | -rw-r--r-- | 14.6 KB |
virtio_mmio.c | -rw-r--r-- | 16.8 KB |
virtio_pci.c | -rw-r--r-- | 21.0 KB |
virtio_ring.c | -rw-r--r-- | 21.8 KB |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...