From: syzbot <syzbot+a437546ec71b04dfb5ac@syzkaller.appspotmail.com>
To: keescook@chromium.org, linux-kernel@vger.kernel.org,
miaoqinglang@huawei.com, qiang.zhang@windriver.com,
swboyd@chromium.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de
Subject: [syzbot] WARNING: ODEBUG bug in corrupted (2)
Date: Mon, 31 May 2021 10:25:23 -0700 [thread overview]
Message-ID: <000000000000b1c43105c3a38257@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: d7c5303f Merge tag 'net-5.13-rc4' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=122fa2b5d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=770708ea7cfd4916
dashboard link: https://syzkaller.appspot.com/bug?extid=a437546ec71b04dfb5ac
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=155e106bd00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a437546ec71b04dfb5ac@syzkaller.appspotmail.com
smsmdtv:smscore_start_device: set device mode failed , rc -22
smsusb:smsusb_init_device: smscore_start_device(...) failed
------------[ cut here ]------------
ODEBUG: free active (active state 0) object type: work_struct hint: do_submit_urb+0x0/0x3e0 drivers/media/usb/siano/smsusb.c:146
WARNING: CPU: 1 PID: 27 at lib/debugobjects.c:505 debug_print_object+0x16e/0x250 lib/debugobjects.c:505
Modules linked in:
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2021-05-31 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 17:25 syzbot [this message]
2021-12-29 0:16 ` syzbot
2021-12-29 5:41 ` Stephen Boyd
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=000000000000b1c43105c3a38257@google.com \
--to=syzbot+a437546ec71b04dfb5ac@syzkaller.appspotmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miaoqinglang@huawei.com \
--cc=qiang.zhang@windriver.com \
--cc=swboyd@chromium.org \
--cc=syzkaller-bugs@googlegroups.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
all inboxes | Powered by JetHome®