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 DBB83C636D4 for ; Fri, 24 Nov 2023 04:19:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230198AbjKXEHS (ORCPT ); Thu, 23 Nov 2023 23:07:18 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51142 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229453AbjKXEHP (ORCPT ); Thu, 23 Nov 2023 23:07:15 -0500 Received: from mail-pl1-f208.google.com (mail-pl1-f208.google.com [209.85.214.208]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F1BA8D56 for ; Thu, 23 Nov 2023 20:07:19 -0800 (PST) Received: by mail-pl1-f208.google.com with SMTP id d9443c01a7336-1cc281f1214so16353115ad.2 for ; Thu, 23 Nov 2023 20:07:19 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700798839; x=1701403639; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=h0vRuOm3bYedFbYqbLhxDQ5YfI/esjpwLN9DwiNIFQ8=; b=r9x2r+hZrlfaayTytXNxPaZITq13rCSad4Xsih230LO1KuRjoieUOd9DMbA6Wq2yUZ XoqKmfrbhnT+T8trOYuQSUxHZeLk/RGCxOmQVHDFrhGpqkhlUhbLz7JDwaMXpTqz19Kd +T1YdKaWzXHS9MTla9wLxWswlhdhI4/oeHHYkKb0B5zwsclutH6H4wnw1QcHD+RMHEtC UCsxAF7GiwvaUuy0S9v0+ZvJg6UQRaUNpEMpC9VkX0jDCbz0kMOi133M/wdfCYShtG+Q 50Mg8yYsD0DBJFLnOU1pIqp3JhrMSmiw7prluc/T2GqVDJyxzh+yymmVCH9y8ZCxB22R QVdA== X-Gm-Message-State: AOJu0Yx9VyEOHUo81xIhKu7d0+o7CrCt+WZYOZNYlSHQavyD7o0AG4ju eMLBD0r1W5hD/kBg98AkvwDXxepH03HyOm/GAcirHLqc+N+j X-Google-Smtp-Source: AGHT+IHZRsewILwuiH0XfYhzpcc84TnIwHPhnSJafwQ5uSyAIc6bJMXvt5C0NCc/uA2o/BuZhV4Ek2XWQlFjz0aEbVOdqG/fV7zE MIME-Version: 1.0 X-Received: by 2002:a17:903:22d2:b0:1cc:42bf:5c1f with SMTP id y18-20020a17090322d200b001cc42bf5c1fmr380444plg.4.1700798839555; Thu, 23 Nov 2023 20:07:19 -0800 (PST) Date: Thu, 23 Nov 2023 20:07:19 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000aa8c0c060ade165e@google.com> Subject: [syzbot] [btrfs?] memory leak in clear_state_bit From: syzbot To: clm@fb.com, dsterba@suse.com, josef@toxicpanda.com, linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.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: 98b1cc82c4af Linux 6.7-rc2 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1617a610e80000 kernel config: https://syzkaller.appspot.com/x/.config?x=f1b9d95ada516af dashboard link: https://syzkaller.appspot.com/bug?extid=81670362c283f3dd889c 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=10e5bdd4e80000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13b506f0e80000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/6b6d520f592c/disk-98b1cc82.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/c2cb6183fd56/vmlinux-98b1cc82.xz kernel image: https://storage.googleapis.com/syzbot-assets/de520cfc8b93/bzImage-98b1cc82.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/97f709bf4312/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+81670362c283f3dd889c@syzkaller.appspotmail.com write to /proc/sys/kernel/softlockup_all_cpu_backtrace failed: No such file or directory BUG: memory leak unreferenced object 0xffff888100812800 (size 64): comm "syz-executor358", pid 5076, jiffies 4294970941 (age 12.950s) hex dump (first 32 bytes): 00 00 48 00 00 00 00 00 ff ff 48 00 00 00 00 00 ..H.......H..... 60 b6 52 02 00 c9 ff ff 60 b6 52 02 00 c9 ff ff `.R.....`.R..... 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] [] ulist_add_merge fs/btrfs/ulist.c:210 [inline] [] ulist_add_merge+0xcb/0x2b0 fs/btrfs/ulist.c:198 [] add_extent_changeset fs/btrfs/extent-io-tree.c:199 [inline] [] add_extent_changeset fs/btrfs/extent-io-tree.c:186 [inline] [] clear_state_bit+0xa4/0x1f0 fs/btrfs/extent-io-tree.c:559 [] __clear_extent_bit+0x432/0x840 fs/btrfs/extent-io-tree.c:731 [] __btrfs_qgroup_release_data+0x21d/0x4a0 fs/btrfs/qgroup.c:4123 [] alloc_ordered_extent+0x57/0x2c0 fs/btrfs/ordered-data.c:159 [] btrfs_alloc_ordered_extent+0x78/0x4f0 fs/btrfs/ordered-data.c:274 [] btrfs_create_dio_extent+0xba/0x1b0 fs/btrfs/inode.c:6953 [] btrfs_get_blocks_direct_write fs/btrfs/inode.c:7343 [inline] [] btrfs_dio_iomap_begin+0xcbc/0x11a0 fs/btrfs/inode.c:7594 [] iomap_iter+0x219/0x590 fs/iomap/iter.c:91 [] __iomap_dio_rw+0x2bb/0xd40 fs/iomap/direct-io.c:658 [] btrfs_dio_write+0x73/0xa0 fs/btrfs/inode.c:7798 [] btrfs_direct_write fs/btrfs/file.c:1543 [inline] [] btrfs_do_write_iter+0x454/0x960 fs/btrfs/file.c:1684 [] call_write_iter include/linux/fs.h:2020 [inline] [] do_iter_readv_writev+0x154/0x220 fs/read_write.c:735 [] do_iter_write+0xec/0x370 fs/read_write.c:860 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 --- 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