All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+3272785b7a1fc9b510f6@syzkaller.appspotmail.com>
To: johan.hedberg@gmail.com, linux-bluetooth@vger.kernel.org,
	 linux-kernel@vger.kernel.org, luiz.dentz@gmail.com,
	marcel@holtmann.org,  syzkaller-bugs@googlegroups.com
Subject: [syzbot] [bluetooth?] WARNING in l2cap_chan_del
Date: Sun, 17 Mar 2024 08:15:25 -0700	[thread overview]
Message-ID: <000000000000e327b00613dcb50d@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    b0546776ad3f Merge tag 'printk-for-6.9' of git://git.kerne..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15bf5b99180000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4ae24324b37fdefe
dashboard link: https://syzkaller.appspot.com/bug?extid=3272785b7a1fc9b510f6
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: i386

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-b0546776.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a07801fab32c/vmlinux-b0546776.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0696c91a7e74/bzImage-b0546776.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3272785b7a1fc9b510f6@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 0 PID: 9 at kernel/workqueue.c:2322 __queue_work+0xc44/0x1170 kernel/workqueue.c:2321
Modules linked in:
CPU: 0 PID: 9 Comm: kworker/0:1 Not tainted 6.8.0-syzkaller-05292-gb0546776ad3f #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Workqueue: events l2cap_chan_timeout
RIP: 0010:__queue_work+0xc44/0x1170 kernel/workqueue.c:2321
Code: 38 d0 7c 09 84 d2 74 05 e8 89 f6 8f 00 8b 5b 2c 31 ff 83 e3 20 89 de e8 5a 64 34 00 85 db 0f 85 fe 00 00 00 e8 6d 69 34 00 90 <0f> 0b 90 e9 1c f9 ff ff e8 5f 69 34 00 90 0f 0b 90 e9 cb f8 ff ff
RSP: 0018:ffffc900003b7ab8 EFLAGS: 00010093
RAX: 0000000000000000 RBX: ffff888014c94000 RCX: ffffffff815ae3ea
RDX: ffff888015704880 RSI: ffffffff815928d3 RDI: ffff888014c94008
RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000200000 R11: 0000000000000004 R12: ffff88801f8648c0
R13: 0000000000000008 R14: ffff88801f8648c8 R15: ffff88804bf9e000
FS:  0000000000000000(0000) GS:ffff88802c200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000030e25000 CR3: 00000000277b0000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 __queue_delayed_work+0x21b/0x2e0 kernel/workqueue.c:2551
 queue_delayed_work_on+0x10e/0x130 kernel/workqueue.c:2595
 queue_delayed_work include/linux/workqueue.h:620 [inline]
 hci_conn_drop include/net/bluetooth/hci_core.h:1621 [inline]
 hci_conn_drop include/net/bluetooth/hci_core.h:1591 [inline]
 l2cap_chan_del+0x5a3/0x930 net/bluetooth/l2cap_core.c:647
 l2cap_chan_close+0xff/0xa30 net/bluetooth/l2cap_core.c:820
 l2cap_chan_timeout+0x17d/0x2f0 net/bluetooth/l2cap_core.c:432
 process_one_work+0x902/0x19d0 kernel/workqueue.c:3254
 process_scheduled_works kernel/workqueue.c:3335 [inline]
 worker_thread+0x6c8/0xf70 kernel/workqueue.c:3416
 kthread+0x2c1/0x3a0 kernel/kthread.c:388
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:243
 </TASK>


---
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.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

                 reply	other threads:[~2024-03-17 15:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=000000000000e327b00613dcb50d@google.com \
    --to=syzbot+3272785b7a1fc9b510f6@syzkaller.appspotmail.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=syzkaller-bugs@googlegroups.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.