void drbd_destroy_mempools(void)
{
if (drbd_request_mempool) mempool_destroy(drbd_request_mempool);
if (drbd_ee_cache) kmem_cache_destroy(drbd_ee_cache);
/* Above code changed from the following function for compatibility
/ with mm3 patches to kernel 2.6.18:
/
/ if (drbd_ee_cache) && kmem_cache_destroy(drbd_ee_cache))
/ printk(KERN_ERR DEVICE_NAME
/ ": kmem_cache_destroy(drbd_ee_cache) FAILED\n");
*/
if (drbd_request_cache) kmem_cache_destroy(drbd_request_cache);
/* Above code changed from the following function for compatability
/ with the mm3 patches to kernel 2.6.18:
/
/ if (drbd_request_cache && kmem_cache_destroy(drbd_request_cache))
/ printk(KERN_ERR DEVICE_NAME
*/
// FIXME what can we do if we fail to destroy them?
i had the same problem (void value not ignored) with feisty and drbd 7.21 and fixed it with the following patch: lists.linbit. com/pipermail/ drbd-user/ 2006-November/ 005918. html
http://
void drbd_destroy_ mempools( void) mempool)
mempool_ destroy( drbd_request_ mempool) ;
kmem_ cache_destroy( drbd_ee_ cache); destroy( drbd_ee_ cache)) destroy( drbd_ee_ cache) FAILED\n"); cache)
kmem_ cache_destroy( drbd_request_ cache);
{
if (drbd_request_
if (drbd_ee_cache)
/* Above code changed from the following function for compatibility
/ with mm3 patches to kernel 2.6.18:
/
/ if (drbd_ee_cache) && kmem_cache_
/ printk(KERN_ERR DEVICE_NAME
/ ": kmem_cache_
*/
if (drbd_request_
/* Above code changed from the following function for compatability destroy( drbd_request_ cache))
/ with the mm3 patches to kernel 2.6.18:
/
/ if (drbd_request_cache && kmem_cache_
/ printk(KERN_ERR DEVICE_NAME
*/
// FIXME what can we do if we fail to destroy them?
return;
}