From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: 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>
Subject: Re: netfilter: active obj WARN when cleaning up
Date: Wed, 27 Nov 2013 00:07:09 +0100 [thread overview]
Message-ID: <20131126230709.GA10948@localhost> (raw)
In-Reply-To: <5294F27D.4000108@oracle.com>
On Tue, Nov 26, 2013 at 02:11:57PM -0500, Sasha Levin wrote:
> Ping? I still see this warning.
Did your test include patch 0c3c6c00c6?
> On 09/07/2013 09:10 AM, Sasha Levin wrote:
> >Hi all,
> >
> >While fuzzing with trinity inside a KVM tools guest, running latest -next kernel, I've
> >stumbled on the following:
> >
> >[ 418.311956] ------------[ cut here ]------------
> >[ 418.312449] WARNING: CPU: 6 PID: 4178 at lib/debugobjects.c:260 debug_print_object+0x8d/0xb0()
> >[ 418.313243] ODEBUG: free active (active state 0) object type: timer_list hint:
> >delayed_work_timer_fn+0x0/0x20
> >[ 418.314038] Modules linked in:
> >[ 418.314038] CPU: 6 PID: 4178 Comm: kworker/u16:2 Tainted: G W 3.11.0-next-20130906-sasha
> >#3984
> >[ 418.314038] Workqueue: netns cleanup_net
> >[ 418.314038] 0000000000000104 ffff880410371a58 ffffffff841b7815 0000000000000104
> >[ 418.314038] ffff880410371aa8 ffff880410371a98 ffffffff8112540c ffff880410371a78
> >[ 418.314038] ffffffff853ea0ab ffff8800bdc68b80 ffffffff85a65c00 ffffffff87676658
> >[ 418.314038] Call Trace:
> >[ 418.314038] [<ffffffff841b7815>] dump_stack+0x52/0x87
> >[ 418.320315] [<ffffffff8112540c>] warn_slowpath_common+0x8c/0xc0
> >[ 418.321040] [<ffffffff811254f6>] warn_slowpath_fmt+0x46/0x50
> >[ 418.321101] [<ffffffff81a60ded>] debug_print_object+0x8d/0xb0
> >[ 418.321101] [<ffffffff811444e0>] ? __queue_work+0x390/0x390
> >[ 418.321101] [<ffffffff81a61605>] __debug_check_no_obj_freed+0xa5/0x220
> >[ 418.321101] [<ffffffff81249e76>] ? kmem_cache_destroy+0x86/0xe0
> >[ 418.321101] [<ffffffff81a61795>] debug_check_no_obj_freed+0x15/0x20
> >[ 418.321101] [<ffffffff812874d7>] kmem_cache_free+0x197/0x340
> >[ 418.321101] [<ffffffff81249e76>] kmem_cache_destroy+0x86/0xe0
> >[ 418.321101] [<ffffffff83d5d681>] nf_conntrack_cleanup_net_list+0x131/0x170
> >[ 418.321101] [<ffffffff83d5ec5d>] nf_conntrack_pernet_exit+0x5d/0x70
> >[ 418.321101] [<ffffffff83cda1ce>] ops_exit_list+0x5e/0x70
> >[ 418.321101] [<ffffffff83cda80b>] cleanup_net+0xfb/0x1c0
> >[ 418.321101] [<ffffffff81145c28>] process_one_work+0x338/0x550
> >[ 418.321101] [<ffffffff81145b50>] ? process_one_work+0x260/0x550
> >[ 418.321883] [<ffffffff81147605>] worker_thread+0x215/0x350
> >[ 418.321883] [<ffffffff811473f0>] ? manage_workers+0x180/0x180
> >[ 418.321883] [<ffffffff81150887>] kthread+0xe7/0xf0
> >[ 418.321883] [<ffffffff811507a0>] ? __init_kthread_worker+0x70/0x70
> >[ 418.321883] [<ffffffff841c7a2c>] ret_from_fork+0x7c/0xb0
> >[ 418.321883] [<ffffffff811507a0>] ? __init_kthread_worker+0x70/0x70
> >[ 418.321883] ---[ end trace c974221542b61d0d ]---
> >
> >
> >Thanks,
> >Sasha
>
next prev parent reply other threads:[~2013-11-26 23:07 UTC|newest]
Thread overview: 55+ 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 [this message]
2013-11-26 23:13 ` Sasha Levin
2013-11-27 10:45 ` Thomas Gleixner
2013-11-27 10:45 ` Thomas Gleixner
2013-11-27 11:39 ` Russell King - ARM Linux
2013-11-27 11:39 ` Russell King - ARM Linux
2013-11-27 13:29 ` Thomas Gleixner
2013-11-27 13:29 ` Thomas Gleixner
2013-11-27 13:32 ` Russell King - ARM Linux
2013-11-27 13:32 ` Russell King - ARM Linux
2013-11-27 13:40 ` Russell King - ARM Linux
2013-11-27 13:40 ` Russell King - ARM Linux
2013-11-27 13:44 ` Thomas Gleixner
2013-11-27 13:44 ` Thomas Gleixner
2013-11-27 23:34 ` Greg KH
2013-11-27 23:34 ` Greg KH
2013-12-02 16:33 ` Christoph Lameter
2013-12-02 16:33 ` Christoph Lameter
2013-12-02 16:40 ` Greg KH
2013-12-02 16:40 ` Greg KH
2013-12-02 17:18 ` Christoph Lameter
2013-12-02 17:18 ` Christoph Lameter
2013-12-02 17:26 ` Greg KH
2013-12-02 17:26 ` Greg KH
2013-12-02 19:00 ` Christoph Lameter
2013-12-02 19:00 ` Christoph Lameter
2013-12-02 19:08 ` Greg KH
2013-12-02 19:08 ` Greg KH
2013-12-02 19:41 ` Christoph Lameter
2013-12-02 19:41 ` Christoph Lameter
2013-12-02 21:22 ` Greg KH
2013-12-02 21:22 ` Greg KH
2013-12-02 21:55 ` Christoph Lameter
2013-12-02 21:55 ` Christoph Lameter
2013-12-02 22:22 ` Greg KH
2013-12-02 22:22 ` Greg KH
2013-12-03 15:22 ` Christoph Lameter
2013-12-03 15:22 ` Christoph Lameter
2013-12-17 19:53 ` Sasha Levin
2013-12-17 19:53 ` Sasha Levin
2013-12-17 20:37 ` Christoph Lameter
2013-12-17 20:37 ` Christoph Lameter
2013-12-17 22:09 ` Sasha Levin
2013-12-17 22:09 ` Sasha Levin
2013-12-17 22:09 ` Sasha Levin
2013-12-17 22:01 ` Thomas Gleixner
2013-12-17 22:01 ` Thomas Gleixner
2013-12-19 12:12 ` Bart Van Assche
2013-12-19 12:12 ` Bart Van Assche
2013-12-19 14:20 ` Bart Van Assche
2013-12-19 14:20 ` Bart Van Assche
2013-11-27 13:41 ` Thomas Gleixner
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=20131126230709.GA10948@localhost \
--to=pablo@netfilter.org \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.