aboutsummaryrefslogtreecommitdiffstats
path: root/arch
diff options
context:
space:
mode:
authorMike Isely <isely@pobox.com>2010-05-15 00:30:29 -0300
committerMauro Carvalho Chehab <mchehab@redhat.com>2010-06-01 01:19:58 -0300
commite3a5ee73e7223cda78f2770572c5ad01928496d6 (patch)
treee0d3879a2d0a108ea49159aaf2eeaae395473fd2 /arch
parent7a6ac34848226e315e0d70333bb4ab83190d9f1d (diff)
downloadkernel_samsung_aries-e3a5ee73e7223cda78f2770572c5ad01928496d6.zip
kernel_samsung_aries-e3a5ee73e7223cda78f2770572c5ad01928496d6.tar.gz
kernel_samsung_aries-e3a5ee73e7223cda78f2770572c5ad01928496d6.tar.bz2
V4L/DVB: pvrusb2: Fix kernel oops on device tear-down
pvrusb2: Delete sysfs class device as the _very_ last step, after we're sure that all driver contexts have gone away first. This is important because it appears that there isn't any protection from a struct device instance reference a deleted struct class instance. The assumption in the kernel code appears to be that the class instance is assumed to be around for the life of the device. So we can't let the class instance go away until all referencing device instances are gone; this is ensured by delaying removal of the class instance until after the driver contexts have all gone away. This bug has been present for a very long time but it didn't apparently become malignant until recently (probably because of other changes in the kernel). Signed-off-by: Mike Isely <isely@pobox.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions