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 C702DC27C76 for ; Wed, 25 Jan 2023 10:43:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235663AbjAYKnw (ORCPT ); Wed, 25 Jan 2023 05:43:52 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45234 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235651AbjAYKnl (ORCPT ); Wed, 25 Jan 2023 05:43:41 -0500 Received: from mail-io1-f69.google.com (mail-io1-f69.google.com [209.85.166.69]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 079952DE6A for ; Wed, 25 Jan 2023 02:43:40 -0800 (PST) Received: by mail-io1-f69.google.com with SMTP id t3-20020a6bc303000000b006f7844c6298so10582581iof.23 for ; Wed, 25 Jan 2023 02:43:39 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=PGBXxtvKnwYbmNiNn2X/TAlTxHlmyhsYye8+V98SOS0=; b=BxfgERIBBpOODafn3TNtBt8txuedIrL50dEspo20LVdShMBrvxpD5YOc0ZbzOZefYe OB4mjV7Cr/SGzx8ds0ePhykkmDKrsRhG7NB2ygjuwpTaRVxdvZ4nZv4V+GPOAdsFo6Ce G3moetodj/xMeggAw0yIz9B6+SjyoZPJZe+jQHo0YyqfIpsbH2fun//0cJML6gOtSBH4 5Nqi8XkeUr5Ge5MgIYtr7N5vZp9QZJZ1DhXek9i5UOoMp14kdC81ZIbToa+P/al66St9 VmdfINuHfcdRAvKniA98shxJxT5LXBMJDrkL/fEtfst9+GmVIKlyhTr4JSXFYcoYN9hs cKHA== X-Gm-Message-State: AFqh2kr3T7PrwWCnxoObzmqKV5ef51QLenKRxASck0oFaazk2oPTkVfB ZDdcP29eVYtn5R7LELPaSU6ROJW3rA87823Ri86qvTE5Hb++ X-Google-Smtp-Source: AMrXdXu0Xt9mkoAmqfb+AAu0/0TNAK9UJLJpWcaRBzn8YQn3SO66TfinmhnepornIPRbVTg04b/geaHwJ9cMXOOT9GyKvc9BGoH7 MIME-Version: 1.0 X-Received: by 2002:a92:60e:0:b0:30e:eb8e:6c13 with SMTP id x14-20020a92060e000000b0030eeb8e6c13mr4262555ilg.27.1674643419338; Wed, 25 Jan 2023 02:43:39 -0800 (PST) Date: Wed, 25 Jan 2023 02:43:39 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000229e6205f3144e05@google.com> Subject: [syzbot] [btrfs?] VFS: Busy inodes after unmount (use-after-free) From: syzbot To: clm@fb.com, dsterba@suse.com, josef@toxicpanda.com, linux-btrfs@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-btrfs@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: edb2f0dc90f2 Merge branch 'for-next/core' into for-kernelci git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci console output: https://syzkaller.appspot.com/x/log.txt?x=1484d22e480000 kernel config: https://syzkaller.appspot.com/x/.config?x=a1c301efa2b11613 dashboard link: https://syzkaller.appspot.com/bug?extid=0af00f6a2cba2058b5db compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2 userspace arch: arm64 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15e20341480000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=154fa4f1480000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/ca1677dc6969/disk-edb2f0dc.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/22527595a2dd/vmlinux-edb2f0dc.xz kernel image: https://storage.googleapis.com/syzbot-assets/45308e5f6962/Image-edb2f0dc.gz.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/6105a892b6d5/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+0af00f6a2cba2058b5db@syzkaller.appspotmail.com VFS: Busy inodes after unmount of loop0. Self-destruct in 5 seconds. Have a nice day... VFS: Busy inodes after unmount of loop0. Self-destruct in 5 seconds. Have a nice day... --- 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