search for: release_dev

Displaying 10 results from an estimated 10 matches for "release_dev".

Did you mean: release_db
2011 Mar 14
1
[PATCH] virtio_pci: Prevent double-free of pci regions after device hot-unplug
...umed to be gone. When the port is finally released (close() called), we call device_destroy() on the port's device. This results in the parent device's structures to be freed as well. This includes the PCI regions for the virtio-console PCI device. Once this is done, however, virtio_pci_release_dev() kicks in, as the last ref to the virtio device is now gone, and attempts to do pci_iounmap(pci_dev, vp_dev->ioaddr); pci_release_regions(pci_dev); pci_disable_device(pci_dev); which results in a double-free warning. Move the code that releases regions, etc., to the virtio_pci...
2011 Mar 14
1
[PATCH] virtio_pci: Prevent double-free of pci regions after device hot-unplug
...umed to be gone. When the port is finally released (close() called), we call device_destroy() on the port's device. This results in the parent device's structures to be freed as well. This includes the PCI regions for the virtio-console PCI device. Once this is done, however, virtio_pci_release_dev() kicks in, as the last ref to the virtio device is now gone, and attempts to do pci_iounmap(pci_dev, vp_dev->ioaddr); pci_release_regions(pci_dev); pci_disable_device(pci_dev); which results in a double-free warning. Move the code that releases regions, etc., to the virtio_pci...
2020 Aug 13
1
[PATCH 06/20] drm/i915: Introduce GEM object functions
...static struct drm_driver mock_driver = { > .name = "mock", > .driver_features = DRIVER_GEM, > .release = mock_device_release, > - > - .gem_close_object = i915_gem_close_object, > - .gem_free_object_unlocked = i915_gem_free_object, > }; > > static void release_dev(struct device *dev) -- Jani Nikula, Intel Open Source Graphics Center
2005 Apr 05
0
Help Disecting kernel crash with ldisc
...sydlxfw01 kernel: Code: 54 24 34 90 8d b4 26 00 00 00 00 b9 02 00 00 00 89 fa b8 2c b2 30 c0 e8 cf 3a f4 ff 89 1c 24 e8 07 ff ff ff 85 c0 75 07 e8 fe ed <09> 00 eb dc 89 fa b8 2c b2 30 c0 e8 f0 3b f4 ff 8b 7b 54 85 ff Apr 5 20:00:21 sydlxfw01 kernel: ve! Apr 5 20:00:21 sydlxfw01 kernel: release_dev: ptm4: read/write wait queue active! Apr 5 20:00:22 sydlxfw01 last message repeated 11689 times ================ I seem to get lots of "release_dev: ptm4: read/write wait queue active!" messages It seems to be in tty_ldisc_ref, but I could be wrong. How do I go about diagnosing the p...
2020 Aug 13
0
[PATCH 06/20] drm/i915: Introduce GEM object functions
...selftests/mock_gem_device.c @@ -86,9 +86,6 @@ static struct drm_driver mock_driver = { .name = "mock", .driver_features = DRIVER_GEM, .release = mock_device_release, - - .gem_close_object = i915_gem_close_object, - .gem_free_object_unlocked = i915_gem_free_object, }; static void release_dev(struct device *dev) -- 2.28.0
2020 Sep 15
0
[PATCH v2 06/21] drm/i915: Introduce GEM object functions
...selftests/mock_gem_device.c @@ -87,9 +87,6 @@ static struct drm_driver mock_driver = { .name = "mock", .driver_features = DRIVER_GEM, .release = mock_device_release, - - .gem_close_object = i915_gem_close_object, - .gem_free_object_unlocked = i915_gem_free_object, }; static void release_dev(struct device *dev) -- 2.28.0
2002 Dec 06
1
Assertion failure in do_get_write_access() at fs/jbd/transaction.c:746
...d3d>] console_callback+0x9/0xb8 [<c011f8f4>] flush_workqueue+0xfc/0x1a8 [<c01d7d34>] console_callback+0x0/0xb8 [<c0111860>] default_wake_function+0x0/0x34 [<c0111860>] default_wake_function+0x0/0x34 [<c011fbd5>] flush_scheduled_work+0xd/0x14 [<c01c8f24>] release_dev+0x544/0x558 [<c01270b6>] free_hot_page+0xa/0x10 [<c012b060>] __page_cache_release+0x80/0x88 [<c0136c16>] free_page_and_swap_cache+0x52/0x5c [<c012709e>] free_hot_cold_page+0xc6/0xd4 [<c01c92de>] tty_release+0x2a/0x68 [<c013b2d7>] __fput+0x3b/0x104 [<c01...
2020 Aug 13
28
[PATCH 00/20] Convert all remaining drivers to GEM object functions
The GEM and PRIME related callbacks in struct drm_driver are deprecated in favor of GEM object functions in struct drm_gem_object_funcs. This patchset converts the remaining drivers to object functions and removes most of the obsolete interfaces. Patches #1 to #18 convert DRM drivers to GEM object functions, one by one. Each patch moves existing callbacks from struct drm_driver to an instance of
2020 Sep 15
40
[PATCH v2 00/21] Convert all remaining drivers to GEM object functions
The GEM and PRIME related callbacks in struct drm_driver are deprecated in favor of GEM object functions in struct drm_gem_object_funcs. This patchset converts the remaining drivers to object functions and removes most of the obsolete interfaces. Patches #1 to #16 and #18 to #19 convert DRM drivers to GEM object functions, one by one. Each patch moves existing callbacks from struct drm_driver to
2020 Sep 23
25
[PATCH v3 00/22] Convert all remaining drivers to GEM object functions
The GEM and PRIME related callbacks in struct drm_driver are deprecated in favor of GEM object functions in struct drm_gem_object_funcs. This patchset converts the remaining drivers to object functions and removes most of the obsolete interfaces. Version 3 of this patchset mostly fixes drm_gem_prime_handle_to_fd and updates i.MX's dcss driver. The driver was missing from earlier versions and