From: Greg KH <greg@kroah.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: linux-usb@vger.kernel.org, Dave Jones <davej@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: usb: mon: freeing active timer
Date: Thu, 24 Apr 2014 12:24:06 -0700 [thread overview]
Message-ID: <20140424192406.GA6054@kroah.com> (raw)
In-Reply-To: <53594C7E.1080407@oracle.com>
On Thu, Apr 24, 2014 at 01:40:14PM -0400, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running the latest -next
> kernel I've stumbled on the following:
>
> [ 1361.390880] WARNING: CPU: 10 PID: 24274 at lib/debugobjects.c:260 debug_print_object+0x8c/0xb0()
> [ 1361.391203] ODEBUG: free active (active state 0) object type: timer_list hint: delayed_work_timer_fn+0x0/0x20
> [ 1361.391203] Modules linked in:
> [ 1361.391203] CPU: 10 PID: 24274 Comm: trinity-c83 Not tainted 3.15.0-rc2-next-20140423-sasha-00018-gc4ff6c4 #408
> [ 1361.391203] 0000000000000009 ffff8801de341c78 ffffffffb85271f2 0000000000000001
> [ 1361.391203] ffff8801de341cc8 ffff8801de341cb8 ffffffffb515afcc ffff8801eb3ebd98
> [ 1361.391203] ffff8801eb751870 ffffffffb9e76200 ffffffffb98dc502 ffffffffbc702550
> [ 1361.391203] Call Trace:
> [ 1361.391203] dump_stack (lib/dump_stack.c:52)
> [ 1361.391203] warn_slowpath_common (kernel/panic.c:430)
> [ 1361.391203] warn_slowpath_fmt (kernel/panic.c:445)
> [ 1361.391203] debug_print_object (lib/debugobjects.c:262)
> [ 1361.391203] ? __queue_work (kernel/workqueue.c:1452)
> [ 1361.391203] __debug_check_no_obj_freed (lib/debugobjects.c:697)
> [ 1361.391203] debug_check_no_obj_freed (lib/debugobjects.c:726)
> [ 1361.391203] kmem_cache_free (mm/slub.c:2689 mm/slub.c:2717)
> [ 1361.391203] ? kmem_cache_destroy (mm/slab_common.c:363)
> [ 1361.391203] kmem_cache_destroy (mm/slab_common.c:363)
> [ 1361.391203] mon_text_release (drivers/usb/mon/mon_text.c:643)
> [ 1361.391203] __fput (fs/file_table.c:217)
> [ 1361.391203] ____fput (fs/file_table.c:253)
> [ 1361.391203] task_work_run (kernel/task_work.c:125 (discriminator 1))
> [ 1361.391203] do_notify_resume (include/linux/tracehook.h:196 arch/x86/kernel/signal.c:751)
> [ 1361.391203] int_signal (arch/x86/kernel/entry_64.S:807)
So you were running usbmon at the time? Were you actually monitoring a
specific USB device/bus, or something else?
thanks,
greg k-h
next prev parent reply other threads:[~2014-04-24 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 17:40 usb: mon: freeing active timer Sasha Levin
2014-04-24 19:24 ` Greg KH [this message]
2014-04-24 19:35 ` Sasha Levin
2014-04-24 19:54 ` Alan Stern
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=20140424192406.GA6054@kroah.com \
--to=greg@kroah.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox