[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131127133231.GO16735@n2100.arm.linux.org.uk>
Date: Wed, 27 Nov 2013 13:32:31 +0000
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Pablo Neira Ayuso <pablo@...filter.org>,
Sasha Levin <sasha.levin@...cle.com>,
Patrick McHardy <kaber@...sh.net>, kadlec@...ckhole.kfki.hu,
"David S. Miller" <davem@...emloft.net>,
netfilter-devel@...r.kernel.org, coreteam@...filter.org,
netdev@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>,
Christoph Lameter <cl@...ux-foundation.org>,
Greg KH <greg@...ah.com>
Subject: Re: netfilter: active obj WARN when cleaning up
On Wed, Nov 27, 2013 at 02:29:41PM +0100, Thomas Gleixner wrote:
> Though the kobject is the only thing which has a delayed work embedded
> inside struct kmem_cache. And the debug object splat points at the
> kmem_cache_free() of the struct kmem_cache itself. That's why I
> assumed the wreckage around that place. And indeed:
>
> kmem_cache_destroy(s)
> __kmem_cache_shutdown(s)
> sysfs_slab_remove(s)
> ....
> kobject_put(&s->kobj)
> kref_put(&kobj->kref, kobject_release);
> kobject_release(kref)
> #ifdef CONFIG_DEBUG_KOBJECT_RELEASE
> schedule_delayed_work(&kobj->release)
> #else
> kobject_cleanup(kobj)
> #endif
>
> So in the CONFIG_DEBUG_KOBJECT_RELEASE=y case, schedule_delayed_work()
> _IS_ called which arms the timer. debugobjects catches the attempt to
> free struct kmem_cache which contains the armed timer.
You fail to show where the free is in the above path.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists