From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; dkim=none Received: from mail-pl1-f207.google.com (mail-pl1-f207.google.com [209.85.214.207]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0660F9E for ; Sun, 19 Nov 2023 16:09:26 -0800 (PST) Received: by mail-pl1-f207.google.com with SMTP id d9443c01a7336-1cc5ac304e8so47964485ad.1 for ; Sun, 19 Nov 2023 16:09:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700438965; x=1701043765; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=bm9eGPc0RwqPbRbgp3iTFtDeXXeqtjeXeTQl0nd1FoI=; b=unaZNTl6K1CNckzjSyilhg1vR2FMTlzwHFa/u/cax/ao1isSDSBVvmL0BUQTxc2TKP 34Gv5Yb50V9/ayF3rTrozRTmz7CXLztq8HdyvwEnfKpXp25rrRj0vaB0yBLfpLARn7T8 XYfKHpglc0/O46AZBbZJf4INMkBL4gu74u0m4+y3XUK0ly9pp+Ux6+TaKsROOTJTIyBT qfBuhEIWv8xo3mLpAi1IgtJfznzZLhhJydZg8DOfgDsrjVNGrVxnIA1OXqfhFRjTNtP4 pDnuyo/h03JeR+f1Q6omUOHflfxiooHDxjlw7anzF7ci5Q54rHXiPWnePHEybpEkksks TzyQ== X-Gm-Message-State: AOJu0YyyGqLeXQgM9uPml2mF621wDM/gPR9brrQYQqQynDA7d3/v7Vp4 hI8xwgsOB3fI7ISmi2ZjSUi2CD21sH2x9wqM2tuEJzKEc+pH X-Google-Smtp-Source: AGHT+IE+tfsFbkR7yz8cn8gaIyXCEYM3FadsbSsqz2LGgiXDKBu6dN0M+i8azKecC/7TiH14onfmFR9HmffSM7xYWD7i5/LM1Qca Precedence: bulk X-Mailing-List: linux-usb@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a17:902:7792:b0:1cc:4327:8bbc with SMTP id o18-20020a170902779200b001cc43278bbcmr1559454pll.10.1700438965521; Sun, 19 Nov 2023 16:09:25 -0800 (PST) Date: Sun, 19 Nov 2023 16:09:25 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000809328060a8a4c1c@google.com> Subject: [syzbot] [staging?] [usb?] memory leak in _r8712_init_xmit_priv (2) From: syzbot To: Larry.Finger@lwfinger.net, florian.c.schilhabel@googlemail.com, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, linux-staging@lists.linux.dev, linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: c42d9eeef8e5 Merge tag 'hardening-v6.7-rc2' of git://git.k.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=13bff22f680000 kernel config: https://syzkaller.appspot.com/x/.config?x=e71d284dd6560ca8 dashboard link: https://syzkaller.appspot.com/bug?extid=83763e624cfec6b462cb compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1564223f680000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17a7c024e80000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/026cc0fc446f/disk-c42d9eee.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/c4b4d6d092c1/vmlinux-c42d9eee.xz kernel image: https://storage.googleapis.com/syzbot-assets/1865f885e9d6/bzImage-c42d9eee.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+83763e624cfec6b462cb@syzkaller.appspotmail.com executing program BUG: memory leak unreferenced object 0xffff888107a5c000 (size 4096): comm "kworker/1:0", pid 22, jiffies 4294943134 (age 18.720s) hex dump (first 32 bytes): 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 00 ................ backtrace: [] kmemleak_alloc_recursive include/linux/kmemleak.h:42 [inline] [] slab_post_alloc_hook mm/slab.h:766 [inline] [] slab_alloc_node mm/slub.c:3478 [inline] [] __kmem_cache_alloc_node+0x2dd/0x3f0 mm/slub.c:3517 [] kmalloc_trace+0x25/0x90 mm/slab_common.c:1098 [] kmalloc include/linux/slab.h:600 [inline] [] _r8712_init_xmit_priv+0x2b2/0x6e0 drivers/staging/rtl8712/rtl871x_xmit.c:130 [] r8712_init_drv_sw+0xc3/0x290 drivers/staging/rtl8712/os_intfs.c:311 [] r871xu_drv_init+0x1c6/0x920 drivers/staging/rtl8712/usb_intf.c:386 [] usb_probe_interface+0x16b/0x3a0 drivers/usb/core/driver.c:396 [] call_driver_probe drivers/base/dd.c:579 [inline] [] really_probe+0x126/0x440 drivers/base/dd.c:658 [] __driver_probe_device+0xc3/0x190 drivers/base/dd.c:800 [] driver_probe_device+0x2a/0x120 drivers/base/dd.c:830 [] __device_attach_driver+0x104/0x160 drivers/base/dd.c:958 [] bus_for_each_drv+0xcd/0x120 drivers/base/bus.c:457 [] __device_attach+0xfa/0x290 drivers/base/dd.c:1030 [] bus_probe_device+0xca/0xd0 drivers/base/bus.c:532 [] device_add+0x9be/0xc90 drivers/base/core.c:3625 [] usb_set_configuration+0x967/0xc70 drivers/usb/core/message.c:2207 [] usb_generic_driver_probe+0x9c/0xf0 drivers/usb/core/generic.c:238 BUG: memory leak unreferenced object 0xffff888107a59000 (size 4096): comm "kworker/1:0", pid 22, jiffies 4294943134 (age 18.720s) hex dump (first 32 bytes): 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 00 ................ backtrace: [] kmemleak_alloc_recursive include/linux/kmemleak.h:42 [inline] [] slab_post_alloc_hook mm/slab.h:766 [inline] [] slab_alloc_node mm/slub.c:3478 [inline] [] __kmem_cache_alloc_node+0x2dd/0x3f0 mm/slub.c:3517 [] kmalloc_trace+0x25/0x90 mm/slab_common.c:1098 [] kmalloc include/linux/slab.h:600 [inline] [] _r8712_init_xmit_priv+0x2b2/0x6e0 drivers/staging/rtl8712/rtl871x_xmit.c:130 [] r8712_init_drv_sw+0xc3/0x290 drivers/staging/rtl8712/os_intfs.c:311 [] r871xu_drv_init+0x1c6/0x920 drivers/staging/rtl8712/usb_intf.c:386 [] usb_probe_interface+0x16b/0x3a0 drivers/usb/core/driver.c:396 [] call_driver_probe drivers/base/dd.c:579 [inline] [] really_probe+0x126/0x440 drivers/base/dd.c:658 [] __driver_probe_device+0xc3/0x190 drivers/base/dd.c:800 [] driver_probe_device+0x2a/0x120 drivers/base/dd.c:830 [] __device_attach_driver+0x104/0x160 drivers/base/dd.c:958 [] bus_for_each_drv+0xcd/0x120 drivers/base/bus.c:457 [] __device_attach+0xfa/0x290 drivers/base/dd.c:1030 [] bus_probe_device+0xca/0xd0 drivers/base/bus.c:532 [] device_add+0x9be/0xc90 drivers/base/core.c:3625 [] usb_set_configuration+0x967/0xc70 drivers/usb/core/message.c:2207 [] usb_generic_driver_probe+0x9c/0xf0 drivers/usb/core/generic.c:238 BUG: memory leak unreferenced object 0xffff888108475000 (size 4096): comm "kworker/1:0", pid 22, jiffies 4294943134 (age 18.720s) hex dump (first 32 bytes): 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 00 ................ backtrace: [] kmemleak_alloc_recursive include/linux/kmemleak.h:42 [inline] [] slab_post_alloc_hook mm/slab.h:766 [inline] [] slab_alloc_node mm/slub.c:3478 [inline] [] __kmem_cache_alloc_node+0x2dd/0x3f0 mm/slub.c:3517 [] kmalloc_trace+0x25/0x90 mm/slab_common.c:1098 [] kmalloc include/linux/slab.h:600 [inline] [] _r8712_init_xmit_priv+0x2b2/0x6e0 drivers/staging/rtl8712/rtl871x_xmit.c:130 [] r8712_init_drv_sw+0xc3/0x290 drivers/staging/rtl8712/os_intfs.c:311 [] r871xu_drv_init+0x1c6/0x920 drivers/staging/rtl8712/usb_intf.c:386 [] usb_probe_interface+0x16b/0x3a0 drivers/usb/core/driver.c:396 [] call_driver_probe drivers/base/dd.c:579 [inline] [] really_probe+0x126/0x440 drivers/base/dd.c:658 [] __driver_probe_device+0xc3/0x190 drivers/base/dd.c:800 [] driver_probe_device+0x2a/0x120 drivers/base/dd.c:830 [] __device_attach_driver+0x104/0x160 drivers/base/dd.c:958 [] bus_for_each_drv+0xcd/0x120 drivers/base/bus.c:457 [] __device_attach+0xfa/0x290 drivers/base/dd.c:1030 [] bus_probe_device+0xca/0xd0 drivers/base/bus.c:532 [] device_add+0x9be/0xc90 drivers/base/core.c:3625 [] usb_set_configuration+0x967/0xc70 drivers/usb/core/message.c:2207 [] usb_generic_driver_probe+0x9c/0xf0 drivers/usb/core/generic.c:238 --- 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 syzbot to run the reproducer, reply with: #syz test: git://repo/address.git branch-or-commit-hash If you attach or paste a git patch, syzbot will apply it before testing. 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