From: Jiri Slaby <jslaby@suse.cz>
To: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jiri Slaby <jirislaby@gmail.com>
Subject: Re: ODEBUG: free active (active state 0) object type: work_struct hint: flush_to_ldisc+0x0/0x1a0
Date: Wed, 10 Oct 2012 10:11:44 +0200 [thread overview]
Message-ID: <50752DC0.1090508@suse.cz> (raw)
In-Reply-To: <20121010042656.GA32075@redhat.com>
On 10/10/2012 06:26 AM, Dave Jones wrote:
> Just hit this..
That'd be me perhaps. Do you have some serial device connected? Or is it
a pure terminals + ptys? Did you do something special? This very smells
like tty_port is being freed while flushing work_struct is still active.
> WARNING: at lib/debugobjects.c:261 debug_print_object+0x8c/0xb0()
> ODEBUG: free active (active state 0) object type: work_struct hint: flush_to_ldisc+0x0/0x1a0
> Modules linked in: fuse ipt_ULOG nfnetlink tun binfmt_misc nfc caif_socket caif phonet can llc2 pppoe pppox ppp_generic slhc irda crc_ccitt rds af_key decnet rose x25 atm netrom appletalk ipx p8023 psnap p8022 llc ax25 lockd sunrpc bluetooth rfkill ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables kvm_intel usb_debug kvm crc32c_intel ghash_clmulni_intel microcode pcspkr i2c_i801 e1000e uinput i915 video i2c_algo_bit drm_kms_helper drm i2c_core
> Pid: 23707, comm: kworker/3:0 Not tainted 3.6.0+ #26
> Call Trace:
> [<ffffffff8107005f>] warn_slowpath_common+0x7f/0xc0
> [<ffffffff81070156>] warn_slowpath_fmt+0x46/0x50
> [<ffffffff813728fc>] debug_print_object+0x8c/0xb0
> [<ffffffff8141c200>] ? tty_insert_flip_string_fixed_flag+0x100/0x100
> [<ffffffff81373699>] debug_check_no_obj_freed+0x119/0x210
> [<ffffffff814122c6>] ? free_tty_struct+0x46/0x50
> [<ffffffff811cd166>] kfree+0xe6/0x340
> [<ffffffff814122c6>] free_tty_struct+0x46/0x50
> [<ffffffff81412377>] release_one_tty+0xa7/0xc0
> [<ffffffff81094bc7>] process_one_work+0x207/0x770
> [<ffffffff81094b57>] ? process_one_work+0x197/0x770
> [<ffffffff814122d0>] ? free_tty_struct+0x50/0x50
> [<ffffffff8109550e>] worker_thread+0x15e/0x440
> [<ffffffff810953b0>] ? rescuer_thread+0x240/0x240
> [<ffffffff8109c25d>] kthread+0xed/0x100
> [<ffffffff816bdcd9>] ? sub_preempt_count+0x79/0xd0
> [<ffffffff816c34a4>] kernel_thread_helper+0x4/0x10
> [<ffffffff810aa29c>] ? finish_task_switch+0x7c/0x120
> [<ffffffff816b92bb>] ? _raw_spin_unlock_irq+0x4b/0x80
> [<ffffffff816b9d37>] ? retint_restore_args+0x13/0x13
> [<ffffffff8109c170>] ? kthread_create_on_node+0x160/0x160
> [<ffffffff816c34a0>] ? gs_change+0x13/0x13
thanks,
--
js
suse labs
next prev parent reply other threads:[~2012-10-10 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 4:26 ODEBUG: free active (active state 0) object type: work_struct hint: flush_to_ldisc+0x0/0x1a0 Dave Jones
2012-10-10 8:11 ` Jiri Slaby [this message]
2012-10-10 14:56 ` Dave Jones
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=50752DC0.1090508@suse.cz \
--to=jslaby@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@redhat.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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