On domenica 27 marzo 2022 22:08:18 CEST syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit: 6b1f86f8e9c7 Merge tag 'folio-5.18b' of git://git.infradea.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=13b41dcb700000 > kernel config: https://syzkaller.appspot.com/x/.config?x=c6e80763d853259b > dashboard link: https://syzkaller.appspot.com/bug?extid=f08c77040fa163a75a46 > 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=1564ecb3700000 > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > Reported-by: syzbot+f08c77040fa163a75a46@syzkaller.appspotmail.com > > BUG: memory leak > unreferenced object 0xffff888118503c00 (size 192): > comm "kworker/u4:2", pid 52, jiffies 4294961137 (age 11.420s) > hex dump (first 32 bytes): > 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 02 00 00 00 06 00 00 00 01 00 00 00 00 00 00 00 ................ > backtrace: > [] kmalloc_node include/linux/slab.h:602 [inline] > [] kzalloc_node include/linux/slab.h:728 [inline] > [] blk_mq_init_tags+0x4b/0xc0 block/blk-mq-tag.c:578 > [] blk_mq_alloc_rq_map+0xea/0x1a0 block/blk-mq.c:3169 > [] blk_mq_alloc_map_and_rqs+0x26/0xb0 block/blk-mq.c:3620 > [] blk_mq_sched_alloc_map_and_rqs block/blk-mq-sched.c:507 [inline] > [] blk_mq_init_sched+0x127/0x2e0 block/blk-mq-sched.c:587 > [] elevator_init_mq+0x1f9/0x240 block/elevator.c:709 > [] device_add_disk+0x25/0x510 block/genhd.c:421 > [] sd_probe+0x457/0x670 drivers/scsi/sd.c:3551 > [] call_driver_probe drivers/base/dd.c:517 [inline] > [] really_probe.part.0+0xe7/0x380 drivers/base/dd.c:596 > [] really_probe drivers/base/dd.c:558 [inline] > [] __driver_probe_device+0x10c/0x1e0 drivers/base/dd.c:755 > [] driver_probe_device+0x2a/0x120 drivers/base/dd.c:785 > [] __device_attach_driver+0xf6/0x140 drivers/base/dd.c:902 > [] bus_for_each_drv+0xb7/0x100 drivers/base/bus.c:427 > [] __device_attach_async_helper+0xcf/0x110 drivers/base/dd.c:931 > [] async_run_entry_fn+0x24/0xf0 kernel/async.c:127 > [] process_one_work+0x2bf/0x600 kernel/workqueue.c:2307 > [] worker_thread+0x59/0x5b0 kernel/workqueue.c:2454 > > BUG: memory leak > unreferenced object 0xffff888117fee680 (size 128): > comm "kworker/u4:2", pid 52, jiffies 4294961137 (age 11.420s) > hex dump (first 32 bytes): > 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > backtrace: > [] kmalloc_array_node include/linux/slab.h:679 [inline] > [] kcalloc_node include/linux/slab.h:684 [inline] > [] sbitmap_init_node+0xde/0x2d0 lib/sbitmap.c:113 > [] sbitmap_queue_init_node+0x3c/0x1f0 lib/sbitmap.c:428 > [] bt_alloc block/blk-mq-tag.c:543 [inline] > [] blk_mq_init_bitmaps+0x57/0xf0 block/blk-mq-tag.c:555 > [] blk_mq_init_tags+0x88/0xc0 block/blk-mq-tag.c:586 > [] blk_mq_alloc_rq_map+0xea/0x1a0 block/blk-mq.c:3169 > [] blk_mq_alloc_map_and_rqs+0x26/0xb0 block/blk-mq.c:3620 > [] blk_mq_sched_alloc_map_and_rqs block/blk-mq-sched.c:507 [inline] > [] blk_mq_init_sched+0x127/0x2e0 block/blk-mq-sched.c:587 > [] elevator_init_mq+0x1f9/0x240 block/elevator.c:709 > [] device_add_disk+0x25/0x510 block/genhd.c:421 > [] sd_probe+0x457/0x670 drivers/scsi/sd.c:3551 > [] call_driver_probe drivers/base/dd.c:517 [inline] > [] really_probe.part.0+0xe7/0x380 drivers/base/dd.c:596 > [] really_probe drivers/base/dd.c:558 [inline] > [] __driver_probe_device+0x10c/0x1e0 drivers/base/dd.c:755 > [] driver_probe_device+0x2a/0x120 drivers/base/dd.c:785 > [] __device_attach_driver+0xf6/0x140 drivers/base/dd.c:902 > [] bus_for_each_drv+0xb7/0x100 drivers/base/bus.c:427 > [] __device_attach_async_helper+0xcf/0x110 drivers/base/dd.c:931 > > BUG: memory leak > unreferenced object 0xffff888116df4c00 (size 512): > comm "kworker/u4:2", pid 52, jiffies 4294961137 (age 11.420s) > hex dump (first 32 bytes): > 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 10 4c df 16 81 88 ff ff 10 4c df 16 81 88 ff ff .L.......L...... > backtrace: > [] kmalloc_node include/linux/slab.h:602 [inline] > [] kzalloc_node include/linux/slab.h:728 [inline] > [] sbitmap_queue_init_node+0x108/0x1f0 lib/sbitmap.c:438 > [] bt_alloc block/blk-mq-tag.c:543 [inline] > [] blk_mq_init_bitmaps+0x87/0xf0 block/blk-mq-tag.c:557 > [] blk_mq_init_tags+0x88/0xc0 block/blk-mq-tag.c:586 > [] blk_mq_alloc_rq_map+0xea/0x1a0 block/blk-mq.c:3169 > [] blk_mq_alloc_map_and_rqs+0x26/0xb0 block/blk-mq.c:3620 > [] blk_mq_sched_alloc_map_and_rqs block/blk-mq-sched.c:507 [inline] > [] blk_mq_init_sched+0x127/0x2e0 block/blk-mq-sched.c:587 > [] elevator_init_mq+0x1f9/0x240 block/elevator.c:709 > [] device_add_disk+0x25/0x510 block/genhd.c:421 > [] sd_probe+0x457/0x670 drivers/scsi/sd.c:3551 > [] call_driver_probe drivers/base/dd.c:517 [inline] > [] really_probe.part.0+0xe7/0x380 drivers/base/dd.c:596 > [] really_probe drivers/base/dd.c:558 [inline] > [] __driver_probe_device+0x10c/0x1e0 drivers/base/dd.c:755 > [] driver_probe_device+0x2a/0x120 drivers/base/dd.c:785 > [] __device_attach_driver+0xf6/0x140 drivers/base/dd.c:902 > [] bus_for_each_drv+0xb7/0x100 drivers/base/bus.c:427 > [] __device_attach_async_helper+0xcf/0x110 drivers/base/dd.c:931 > [] async_run_entry_fn+0x24/0xf0 kernel/async.c:127 > > > > --- > 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 > > -- > You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group. > To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/000000000000c341cc05db38c1b0%40google.com. > Oh, now I see that both the failures of device_add() or device_add_disk() should make the code to jump to the "out_free_index" label. Even if my first change was tested and didn't trigger any issue, I'd like to try again with both changes too. #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master Fabio M. De Francesco