From: syzbot <syzbot+01321b15cc98e6bf96d6@syzkaller.appspotmail.com>
To: axboe@kernel.dk, cgroups@vger.kernel.org,
gregkh@linuxfoundation.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org,
noreply@bizcloud-server.changyang.com.tw, sashal@kernel.org,
stable@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tj@kernel.org, yanfei.xu@windriver.com
Subject: Re: [syzbot] memory leak in blk_iolatency_init
Date: Sat, 23 Oct 2021 11:58:27 -0700 [thread overview]
Message-ID: <00000000000082261505cf09b69c@google.com> (raw)
In-Reply-To: <0000000000004ee28405cbe8d287@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 9c0c4d24ac00 Merge tag 'block-5.15-2021-10-22' of git://gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1709f5c4b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=d25eeb482b0f99b
dashboard link: https://syzkaller.appspot.com/bug?extid=01321b15cc98e6bf96d6
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=102280acb00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=144b96f8b00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+01321b15cc98e6bf96d6@syzkaller.appspotmail.com
BUG: memory leak
unreferenced object 0xffff888104729800 (size 96):
comm "kworker/u4:2", pid 156, jiffies 4294937755 (age 219.670s)
hex dump (first 32 bytes):
00 49 c9 85 ff ff ff ff e0 b0 8b 03 81 88 ff ff .I..............
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<ffffffff82268cf8>] kmalloc include/linux/slab.h:591 [inline]
[<ffffffff82268cf8>] kzalloc include/linux/slab.h:721 [inline]
[<ffffffff82268cf8>] blk_iolatency_init+0x28/0x190 block/blk-iolatency.c:724
[<ffffffff8225f71e>] blkcg_init_queue+0xee/0x1c0 block/blk-cgroup.c:1193
[<ffffffff82228fca>] blk_alloc_queue+0x22a/0x2e0 block/blk-core.c:584
[<ffffffff8223ee35>] blk_mq_init_queue_data block/blk-mq.c:3119 [inline]
[<ffffffff8223ee35>] __blk_mq_alloc_disk+0x25/0xd0 block/blk-mq.c:3143
[<ffffffff826a187f>] floppy_alloc_disk+0x2f/0x130 drivers/block/floppy.c:4495
[<ffffffff86f2aaa9>] do_floppy_init drivers/block/floppy.c:4566 [inline]
[<ffffffff86f2aaa9>] floppy_async_init+0x10f/0x1329 drivers/block/floppy.c:4731
[<ffffffff81277354>] async_run_entry_fn+0x24/0xf0 kernel/async.c:127
[<ffffffff81265dbf>] process_one_work+0x2cf/0x620 kernel/workqueue.c:2297
[<ffffffff812666c9>] worker_thread+0x59/0x5d0 kernel/workqueue.c:2444
[<ffffffff8126fc48>] kthread+0x188/0x1d0 kernel/kthread.c:319
[<ffffffff810022cf>] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
BUG: memory leak
unreferenced object 0xffff888104729400 (size 96):
comm "kworker/u4:2", pid 156, jiffies 4294937755 (age 219.670s)
hex dump (first 32 bytes):
00 49 c9 85 ff ff ff ff 90 a8 8b 03 81 88 ff ff .I..............
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<ffffffff82268cf8>] kmalloc include/linux/slab.h:591 [inline]
[<ffffffff82268cf8>] kzalloc include/linux/slab.h:721 [inline]
[<ffffffff82268cf8>] blk_iolatency_init+0x28/0x190 block/blk-iolatency.c:724
[<ffffffff8225f71e>] blkcg_init_queue+0xee/0x1c0 block/blk-cgroup.c:1193
[<ffffffff82228fca>] blk_alloc_queue+0x22a/0x2e0 block/blk-core.c:584
[<ffffffff8223ee35>] blk_mq_init_queue_data block/blk-mq.c:3119 [inline]
[<ffffffff8223ee35>] __blk_mq_alloc_disk+0x25/0xd0 block/blk-mq.c:3143
[<ffffffff826a187f>] floppy_alloc_disk+0x2f/0x130 drivers/block/floppy.c:4495
[<ffffffff86f2aaa9>] do_floppy_init drivers/block/floppy.c:4566 [inline]
[<ffffffff86f2aaa9>] floppy_async_init+0x10f/0x1329 drivers/block/floppy.c:4731
[<ffffffff81277354>] async_run_entry_fn+0x24/0xf0 kernel/async.c:127
[<ffffffff81265dbf>] process_one_work+0x2cf/0x620 kernel/workqueue.c:2297
[<ffffffff812666c9>] worker_thread+0x59/0x5d0 kernel/workqueue.c:2444
[<ffffffff8126fc48>] kthread+0x188/0x1d0 kernel/kthread.c:319
[<ffffffff810022cf>] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
BUG: memory leak
unreferenced object 0xffff888104767e00 (size 96):
comm "kworker/u4:2", pid 156, jiffies 4294937755 (age 219.670s)
hex dump (first 32 bytes):
00 49 c9 85 ff ff ff ff 40 a0 8b 03 81 88 ff ff .I......@.......
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<ffffffff82268cf8>] kmalloc include/linux/slab.h:591 [inline]
[<ffffffff82268cf8>] kzalloc include/linux/slab.h:721 [inline]
[<ffffffff82268cf8>] blk_iolatency_init+0x28/0x190 block/blk-iolatency.c:724
[<ffffffff8225f71e>] blkcg_init_queue+0xee/0x1c0 block/blk-cgroup.c:1193
[<ffffffff82228fca>] blk_alloc_queue+0x22a/0x2e0 block/blk-core.c:584
[<ffffffff8223ee35>] blk_mq_init_queue_data block/blk-mq.c:3119 [inline]
[<ffffffff8223ee35>] __blk_mq_alloc_disk+0x25/0xd0 block/blk-mq.c:3143
[<ffffffff826a187f>] floppy_alloc_disk+0x2f/0x130 drivers/block/floppy.c:4495
[<ffffffff86f2aaa9>] do_floppy_init drivers/block/floppy.c:4566 [inline]
[<ffffffff86f2aaa9>] floppy_async_init+0x10f/0x1329 drivers/block/floppy.c:4731
[<ffffffff81277354>] async_run_entry_fn+0x24/0xf0 kernel/async.c:127
[<ffffffff81265dbf>] process_one_work+0x2cf/0x620 kernel/workqueue.c:2297
[<ffffffff812666c9>] worker_thread+0x59/0x5d0 kernel/workqueue.c:2444
[<ffffffff8126fc48>] kthread+0x188/0x1d0 kernel/kthread.c:319
[<ffffffff810022cf>] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
BUG: memory leak
unreferenced object 0xffff888104767500 (size 96):
comm "kworker/u4:2", pid 156, jiffies 4294937755 (age 219.670s)
hex dump (first 32 bytes):
00 49 c9 85 ff ff ff ff 60 31 88 03 81 88 ff ff .I......`1......
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<ffffffff82268cf8>] kmalloc include/linux/slab.h:591 [inline]
[<ffffffff82268cf8>] kzalloc include/linux/slab.h:721 [inline]
[<ffffffff82268cf8>] blk_iolatency_init+0x28/0x190 block/blk-iolatency.c:724
[<ffffffff8225f71e>] blkcg_init_queue+0xee/0x1c0 block/blk-cgroup.c:1193
[<ffffffff82228fca>] blk_alloc_queue+0x22a/0x2e0 block/blk-core.c:584
[<ffffffff8223ee35>] blk_mq_init_queue_data block/blk-mq.c:3119 [inline]
[<ffffffff8223ee35>] __blk_mq_alloc_disk+0x25/0xd0 block/blk-mq.c:3143
[<ffffffff826a187f>] floppy_alloc_disk+0x2f/0x130 drivers/block/floppy.c:4495
[<ffffffff86f2aaa9>] do_floppy_init drivers/block/floppy.c:4566 [inline]
[<ffffffff86f2aaa9>] floppy_async_init+0x10f/0x1329 drivers/block/floppy.c:4731
[<ffffffff81277354>] async_run_entry_fn+0x24/0xf0 kernel/async.c:127
[<ffffffff81265dbf>] process_one_work+0x2cf/0x620 kernel/workqueue.c:2297
[<ffffffff812666c9>] worker_thread+0x59/0x5d0 kernel/workqueue.c:2444
[<ffffffff8126fc48>] kthread+0x188/0x1d0 kernel/kthread.c:319
[<ffffffff810022cf>] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
write to /proc/sys/kernel/hung_task_check_interval_secs failed: No such file or directory
write to /proc/sys/kernel/softlockup_all_cpu_backtrace failed: No such file or directory
write to /proc/sys/kernel/hung_task_check_interval_secs failed: No such file or directory
write to /proc/sys/kernel/softlockup_all_cpu_backtrace failed: No such file or directory
prev parent reply other threads:[~2021-10-23 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 23:28 [syzbot] memory leak in blk_iolatency_init syzbot
2021-09-13 23:28 ` syzbot
[not found] ` <0000000000004ee28405cbe8d287-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2021-09-14 3:13 ` Xu, Yanfei
2021-09-14 3:13 ` Xu, Yanfei
2021-10-23 18:58 ` 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=00000000000082261505cf09b69c@google.com \
--to=syzbot+01321b15cc98e6bf96d6@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noreply@bizcloud-server.changyang.com.tw \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
--cc=yanfei.xu@windriver.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.