All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+63bed493aebbf6872647@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, bp@alien8.de, davem@davemloft.net,
	hkallweit1@gmail.com, hpa@zytor.com, johan.hedberg@gmail.com,
	kuba@kernel.org, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org, luto@kernel.org,
	marcel@holtmann.org, mingo@redhat.com, netdev@vger.kernel.org,
	syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
	x86@kernel.org
Subject: Re: WARNING in __queue_work (3)
Date: Wed, 09 Dec 2020 03:48:10 -0800	[thread overview]
Message-ID: <0000000000002dd77405b606a278@google.com> (raw)
In-Reply-To: <000000000000c79c6b05ac027164@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    7d8761ba Merge branch 'fixes' of git://git.kernel.org/pub/..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14859745500000
kernel config:  https://syzkaller.appspot.com/x/.config?x=59df2a4dced5f928
dashboard link: https://syzkaller.appspot.com/bug?extid=63bed493aebbf6872647
compiler:       gcc (GCC) 10.1.0-syz 20200507
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1431cc13500000

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 24939 at kernel/workqueue.c:1416 __queue_work+0xb59/0xf00 kernel/workqueue.c:1416
Modules linked in:
CPU: 1 PID: 24939 Comm: syz-executor.3 Not tainted 5.10.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__queue_work+0xb59/0xf00 kernel/workqueue.c:1416
Code: e0 07 83 c0 03 38 d0 7c 09 84 d2 74 05 e8 3f d0 69 00 8b 5b 24 31 ff 83 e3 20 89 de e8 20 4b 28 00 85 db 75 7c e8 c7 52 28 00 <0f> 0b e9 dc fa ff ff e8 bb 52 28 00 0f 0b e9 55 fa ff ff e8 af 52
RSP: 0018:ffffc9000266f750 EFLAGS: 00010093
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff8147b1a0
RDX: ffff88801f184ec0 RSI: ffffffff8147b1a9 RDI: 0000000000000005
RBP: ffff88804d3d4b00 R08: 0000000000000000 R09: ffffffff8f12d1a3
R10: 0000000000000000 R11: 0000000000000000 R12: ffff888059ce4ac8
R13: ffff88803f6b5800 R14: 0000000000000293 R15: ffff88803f6b5800
FS:  00007f4e91751700(0000) GS:ffff8880b9f00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007effff766db8 CR3: 0000000059bc0000 CR4: 0000000000350ee0
Call Trace:
 queue_work_on+0xc7/0xd0 kernel/workqueue.c:1521
 l2cap_do_send+0x248/0x480 net/bluetooth/l2cap_core.c:987
 l2cap_chan_send+0xcc3/0x2ac0 net/bluetooth/l2cap_core.c:2706
 l2cap_sock_sendmsg+0x235/0x2f0 net/bluetooth/l2cap_sock.c:1134
 sock_sendmsg_nosec net/socket.c:651 [inline]
 sock_sendmsg+0xcf/0x120 net/socket.c:671
 ____sys_sendmsg+0x331/0x810 net/socket.c:2353
 ___sys_sendmsg+0xf3/0x170 net/socket.c:2407
 __sys_sendmmsg+0x195/0x470 net/socket.c:2497
 __do_sys_sendmmsg net/socket.c:2526 [inline]
 __se_sys_sendmmsg net/socket.c:2523 [inline]
 __x64_sys_sendmmsg+0x99/0x100 net/socket.c:2523
 do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45e0f9
Code: 0d b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 db b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f4e91750c68 EFLAGS: 00000246 ORIG_RAX: 0000000000000133
RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 000000000045e0f9
RDX: 0000000000000500 RSI: 0000000020003f00 RDI: 0000000000000005
RBP: 000000000119c070 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000119c034
R13: 00007ffd9c18ecaf R14: 00007f4e917519c0 R15: 000000000119c034


      reply	other threads:[~2020-12-09 11:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04  0:36 WARNING in __queue_work (3) syzbot
2020-12-09 11:48 ` syzbot [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=0000000000002dd77405b606a278@google.com \
    --to=syzbot+63bed493aebbf6872647@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=davem@davemloft.net \
    --cc=hkallweit1@gmail.com \
    --cc=hpa@zytor.com \
    --cc=johan.hedberg@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mingo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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.