From: syzbot <syzbot+fedc0f6148b1b9a42593@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] WARNING in percpu_ref_exit (3)
Date: Fri, 19 Mar 2021 02:45:19 -0700 [thread overview]
Message-ID: <000000000000f8ca3305bde0922e@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: bf152b0b Merge tag 'for_linus' of git://git.kernel.org/pub..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14532c1ad00000
kernel config: https://syzkaller.appspot.com/x/.config?x=e2f52d48cfe68458
dashboard link: https://syzkaller.appspot.com/bug?extid=fedc0f6148b1b9a42593
compiler: Debian clang version 11.0.1-2
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+fedc0f6148b1b9a42593@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 68 at lib/percpu-refcount.c:113 __percpu_ref_exit lib/percpu-refcount.c:113 [inline]
WARNING: CPU: 0 PID: 68 at lib/percpu-refcount.c:113 percpu_ref_exit+0x1e0/0x1f0 lib/percpu-refcount.c:134
Modules linked in:
CPU: 1 PID: 68 Comm: kworker/u4:2 Not tainted 5.12.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events_unbound io_ring_exit_work
RIP: 0010:__percpu_ref_exit lib/percpu-refcount.c:113 [inline]
RIP: 0010:percpu_ref_exit+0x1e0/0x1f0 lib/percpu-refcount.c:134
Code: c7 c7 80 67 ce 8c 4c 89 e6 e8 9c 96 84 05 48 8b 3c 24 48 83 c4 10 5b 41 5c 41 5d 41 5e 41 5f 5d e9 65 8b e8 fd e8 00 68 a5 fd <0f> 0b e9 d0 fe ff ff 66 0f 1f 84 00 00 00 00 00 41 57 41 56 41 55
RSP: 0018:ffffc90000fbfba0 EFLAGS: 00010293
RAX: ffffffff83d35710 RBX: 0000607f46034a90 RCX: ffff88801195b780
RDX: 0000000000000000 RSI: 0000607f46034a90 RDI: 0000000000000000
RBP: ffff8880292ae580 R08: ffffffff83d355a5 R09: fffffbfff1f290ca
R10: fffffbfff1f290ca R11: 0000000000000000 R12: ffff8880292ae590
R13: ffff8880121a6000 R14: 1ffff11002434c00 R15: 1ffff11002434c01
FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b32d23000 CR3: 0000000013897000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
io_ring_ctx_free fs/io_uring.c:8419 [inline]
io_ring_exit_work+0x580/0xa90 fs/io_uring.c:8565
process_one_work+0x789/0xfd0 kernel/workqueue.c:2275
worker_thread+0xac1/0x1300 kernel/workqueue.c:2421
kthread+0x39a/0x3c0 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294
---
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.
reply other threads:[~2021-03-19 9:45 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=000000000000f8ca3305bde0922e@google.com \
--to=syzbot+fedc0f6148b1b9a42593@syzkaller.appspotmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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.