From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Farhad Alemi <farhad.alemi@berkeley.edu>
Cc: Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
falemi@asu.edu, greybus-dev@lists.linaro.org,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] greybus: ODEBUG free-active-timer in gb_operation_sync_timeout()
Date: Fri, 28 Aug 2026 08:59:45 +0200 [thread overview]
Message-ID: <2026082839-corny-reputably-a5ff@gregkh> (raw)
In-Reply-To: <CA+0ovChDP9RtBDgTou=xz5Vmsk2hxaRryNCARO5h5JtiMS_OXQ@mail.gmail.com>
On Thu, Aug 27, 2026 at 10:42:25PM -0700, Farhad Alemi wrote:
> Hello,
>
> As part of the kernel research at ASU's SEFCOM
> lab, we hit the crash below. Crash reports can be found here:
>
> https://github.com/farhad-alemi/public_bug_reports/tree/main/165-warning-odebug-bug-in-gb-operation-sync-timeout/
>
> ODEBUG: free active (active state 0) object: ffff888014747a70 object
> type: timer_list hint: gb_operation_timeout+0x0/0x100
> drivers/greybus/operation.c:1265
> WARNING: lib/debugobjects.c:632 at
> debug_check_no_obj_freed+0x3fd/0x540 lib/debugobjects.c:1156, CPU#1:
> kworker/u8:3/10201
> Call Trace:
> kmem_cache_free+0xcb/0x4d0 mm/slub.c:6378
> gb_operation_sync_timeout+0x1c7/0x270 drivers/greybus/operation.c:1172
> gb_operation_sync include/linux/greybus/operation.h:203 [inline]
> gb_svc_dme_peer_get+0x10a/0x250 drivers/greybus/svc.c:428
> gb_interface_read_and_clear_init_status
> drivers/greybus/interface.c:380 [inline]
> gb_interface_enable+0x146/0x900 drivers/greybus/interface.c:1075
> gb_module_register_interface drivers/greybus/module.c:162 [inline]
> gb_module_add+0x1b3/0x3d0 drivers/greybus/module.c:209
>
> Our reproducer.c is available upon request.
>
> Happy to test a patch if that would help.
Again, please send a patch.
prev parent reply other threads:[~2026-08-28 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 5:42 [BUG] greybus: ODEBUG free-active-timer in gb_operation_sync_timeout() Farhad Alemi
2026-08-28 6:59 ` Greg Kroah-Hartman [this message]
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=2026082839-corny-reputably-a5ff@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=elder@kernel.org \
--cc=falemi@asu.edu \
--cc=farhad.alemi@berkeley.edu \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--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 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.