netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
	Sasha Levin <sasha.levin@oracle.com>,
	Patrick McHardy <kaber@trash.net>,
	kadlec@blackhole.kfki.hu, "David S. Miller" <davem@davemloft.net>,
	netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
	netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
	Christoph Lameter <cl@linux-foundation.org>,
	Greg KH <greg@kroah.com>
Subject: Re: netfilter: active obj WARN when cleaning up
Date: Wed, 27 Nov 2013 13:32:31 +0000	[thread overview]
Message-ID: <20131127133231.GO16735@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.02.1311271409280.30673@ionos.tec.linutronix.de>

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.

  reply	other threads:[~2013-11-27 13:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-07 13:10 netfilter: active obj WARN when cleaning up Sasha Levin
2013-11-26 19:11 ` Sasha Levin
2013-11-26 23:07   ` Pablo Neira Ayuso
2013-11-26 23:13     ` Sasha Levin
2013-11-27 10:45     ` Thomas Gleixner
2013-11-27 11:39       ` Russell King - ARM Linux
2013-11-27 13:29         ` Thomas Gleixner
2013-11-27 13:32           ` Russell King - ARM Linux [this message]
2013-11-27 13:40             ` Russell King - ARM Linux
2013-11-27 13:44               ` Thomas Gleixner
2013-11-27 23:34                 ` Greg KH
2013-12-02 16:33                   ` Christoph Lameter
2013-12-02 16:40                     ` Greg KH
2013-12-02 17:18                       ` Christoph Lameter
2013-12-02 17:26                         ` Greg KH
2013-12-02 19:00                           ` Christoph Lameter
2013-12-02 19:08                             ` Greg KH
2013-12-02 19:41                               ` Christoph Lameter
2013-12-02 21:22                                 ` Greg KH
2013-12-02 21:55                                   ` Christoph Lameter
2013-12-02 22:22                                     ` Greg KH
2013-12-03 15:22                                       ` Christoph Lameter
2013-12-17 19:53                                         ` Sasha Levin
2013-12-17 20:37                                           ` Christoph Lameter
2013-12-17 22:09                                             ` Sasha Levin
2013-12-17 22:01                                           ` Thomas Gleixner
2013-12-19 12:12                                           ` Bart Van Assche
2013-12-19 14:20                                             ` Bart Van Assche
2013-11-27 13:41             ` Thomas Gleixner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131127133231.GO16735@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=coreteam@netfilter.org \
    --cc=davem@davemloft.net \
    --cc=greg@kroah.com \
    --cc=kaber@trash.net \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=sasha.levin@oracle.com \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).