Hans Petter Selasky 07da61a6cc Streamline use of cdevpriv and correct some corner cases. ... 1) It is not useful to call "devfs_clear_cdevpriv()" from "d_close" callbacks, hence for example read, write, ioctl and so on might be sleeping at the time of "d_close" being called and then then freed private data can still be accessed. Examples: dtrace, linux_compat, ksyms (all fixed by this patch) 2) In sys/dev/drm* there are some cases in which memory will be freed twice, if open fails, first by code in the open routine, secondly by the cdevpriv destructor. Move registration of the cdevpriv to the end of the drm open routines. 3) devfs_clear_cdevpriv() is not called if the "d_open" callback registered cdevpriv data and the "d_open" callback function returned an error. Fix this. Discussed with: phk MFC after: 2 weeks		2012-08-15 16:19:39 +00:00
..
ati_pcigart.c
drm_agpsupport.c
drm_atomic.h
drm_auth.c
drm_bufs.c
drm_context.c
drm_dma.c
drm_drawable.c
drm_drv.c
drm_fops.c
drm_hashtab.c
drm_hashtab.h
drm_internal.h
drm_ioctl.c
drm_irq.c
drm_linux_list.h
drm_lock.c
drm_memory.c
drm_mm.c
drm_mm.h
drm_pci.c
drm_pciids.h
drm_sarea.h
drm_scatter.c
drm_sman.c
drm_sman.h
drm_sysctl.c
drm_vm.c
drm.h
drmP.h
i915_dma.c
i915_drm.h
i915_drv.c
i915_drv.h
i915_irq.c
i915_mem.c
i915_reg.h
i915_suspend.c
mach64_dma.c
mach64_drm.h
mach64_drv.c
mach64_drv.h
mach64_irq.c
mach64_state.c
mga_dma.c
mga_drm.h
mga_drv.c
mga_drv.h
mga_irq.c
mga_state.c
mga_ucode.h
mga_warp.c
r128_cce.c
r128_drm.h
r128_drv.c
r128_drv.h
r128_irq.c
r128_state.c
r300_cmdbuf.c
r300_reg.h
r600_blit.c
r600_cp.c
r600_microcode.h
radeon_cp.c
radeon_cs.c
radeon_drm.h
radeon_drv.c
radeon_drv.h
radeon_irq.c
radeon_mem.c
radeon_microcode.h
radeon_state.c
savage_bci.c
savage_drm.h
savage_drv.c
savage_drv.h
savage_state.c
sis_drm.h
sis_drv.c
sis_drv.h
sis_ds.c
sis_ds.h
sis_mm.c
tdfx_drv.c
tdfx_drv.h
via_3d_reg.h
via_dma.c
via_dmablit.c
via_dmablit.h
via_drm.h
via_drv.c
via_drv.h
via_irq.c
via_map.c
via_mm.c
via_verifier.c
via_verifier.h
via_video.c