From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1F741C433EF for ; Tue, 24 May 2022 22:40:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242446AbiEXWkd (ORCPT ); Tue, 24 May 2022 18:40:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36994 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229731AbiEXWka (ORCPT ); Tue, 24 May 2022 18:40:30 -0400 Received: from mail-il1-f198.google.com (mail-il1-f198.google.com [209.85.166.198]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 791A57939A for ; Tue, 24 May 2022 15:40:29 -0700 (PDT) Received: by mail-il1-f198.google.com with SMTP id i15-20020a056e0212cf00b002cf3463ed24so11663479ilm.0 for ; Tue, 24 May 2022 15:40:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=3Wu1WB361cVyVmWaFBDq59Mw0eDvd4l+pFg67au8VgE=; b=PeZ7/bnL4RFoXiuL/pspRMc4hUfxE1+qQyxfY3UDpp+8kXnp9pUXQR+eYqnPiul+Mx GltNkzg52LgQl/SyZYKPRZfLOkYdDVwLH4TjD9wOc9FKLLZhubcODiRClrhJhFCcyWd2 mHWUrc59D1umxLLU55ioDaU4AcQHvQzU3+4Z0zPFMurjZmNoDk+8ZEmub58iw+ebZXkC bcwgn9AfOrF8YleZWa9MhePf1G6108XUeERDd8dHdS2TepI3y7Q0ekjIFPMkPVTGzOjP 0nBExxf76bBYvyWczuOWcYQeGV73vfDVB2CFV87NU05JbPOMlftKjUP8YrsSCcs3RdAK bM8Q== X-Gm-Message-State: AOAM5327NK1KLYp7Hk5YV0WYH+QQMGxVqr6GDGSn+3l8wzRT1zBLVtLk SdtME7efVRqhmpqPbcug9WRvmxLNzYMnPqAwDp/FRGvOPQjq X-Google-Smtp-Source: ABdhPJzSV6nT/ASn4hr8gK9r1/+GtK+/qzh6e8zmFmEYkLIDSP7S5sAPXOiKlM2cs0XqhR9VEbkpIPdiO1AXCM2VVjrChe+pK8SX MIME-Version: 1.0 X-Received: by 2002:a05:6e02:20e9:b0:2d1:d151:3c53 with SMTP id q9-20020a056e0220e900b002d1d1513c53mr1815171ilv.220.1653432028356; Tue, 24 May 2022 15:40:28 -0700 (PDT) Date: Tue, 24 May 2022 15:40:28 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000b5e80405dfc9a4f5@google.com> Subject: [syzbot] memory leak in dvb_usb_device_init From: syzbot To: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, mchehab@kernel.org, mudongliangabcd@gmail.com, sean@mess.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: 3d7285a335ed Merge tag 'v5.18-p2' of git://git.kernel.org/.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=13a2f289f00000 kernel config: https://syzkaller.appspot.com/x/.config?x=50f4d49cdcacc43c dashboard link: https://syzkaller.appspot.com/bug?extid=f66dd31987e6740657be 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=131c8871f00000 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+f66dd31987e6740657be@syzkaller.appspotmail.com BUG: memory leak unreferenced object 0xffff8881172f1a00 (size 512): comm "kworker/0:2", pid 139, jiffies 4294994873 (age 10.960s) 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: [] dvb_usb_adapter_init drivers/media/usb/dvb-usb/dvb-usb-init.c:75 [inline] [] dvb_usb_init drivers/media/usb/dvb-usb/dvb-usb-init.c:184 [inline] [] dvb_usb_device_init.cold+0x4e5/0x79e drivers/media/usb/dvb-usb/dvb-usb-init.c:308 [] dib0700_probe+0x8d/0x1b0 drivers/media/usb/dvb-usb/dib0700_core.c:883 [] usb_probe_interface+0x177/0x370 drivers/usb/core/driver.c:396 [] call_driver_probe drivers/base/dd.c:542 [inline] [] really_probe.part.0+0xe7/0x310 drivers/base/dd.c:621 [] really_probe drivers/base/dd.c:583 [inline] [] __driver_probe_device+0x10c/0x1e0 drivers/base/dd.c:752 [] driver_probe_device+0x2a/0x120 drivers/base/dd.c:782 [] __device_attach_driver+0xf6/0x140 drivers/base/dd.c:899 [] bus_for_each_drv+0xb7/0x100 drivers/base/bus.c:427 [] __device_attach+0x122/0x260 drivers/base/dd.c:970 [] bus_probe_device+0xc6/0xe0 drivers/base/bus.c:487 [] device_add+0x5fb/0xdf0 drivers/base/core.c:3405 [] usb_set_configuration+0x8f2/0xb80 drivers/usb/core/message.c:2170 [] usb_generic_driver_probe+0x8c/0xc0 drivers/usb/core/generic.c:238 [] usb_probe_device+0x5c/0x140 drivers/usb/core/driver.c:293 [] call_driver_probe drivers/base/dd.c:542 [inline] [] really_probe.part.0+0xe7/0x310 drivers/base/dd.c:621 [] really_probe drivers/base/dd.c:583 [inline] [] __driver_probe_device+0x10c/0x1e0 drivers/base/dd.c:752 --- 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