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 63015C433EF for ; Thu, 28 Apr 2022 05:05:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238820AbiD1FIa (ORCPT ); Thu, 28 Apr 2022 01:08:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56644 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233716AbiD1FI3 (ORCPT ); Thu, 28 Apr 2022 01:08:29 -0400 Received: from mail-io1-f69.google.com (mail-io1-f69.google.com [209.85.166.69]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 55A78F00 for ; Wed, 27 Apr 2022 22:05:14 -0700 (PDT) Received: by mail-io1-f69.google.com with SMTP id x13-20020a0566022c4d00b0065491fa5614so3790864iov.9 for ; Wed, 27 Apr 2022 22:05:14 -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:in-reply-to:message-id:subject :from:to; bh=NELWs5E3d7hrbPccO9GIG4nHqgSZ2xPQFrfhxPBBI5U=; b=Nwf6OB4cxJS3EC/XRsM4OUW2MsHt5dLH9PCwvFHEX4rSojXxnONPp/BG3r+fPEOO6e VJHBzBIXpAmwO0z42+EDYAX7v3mZhXT10l8zrEwD0V/3iXn22P+rwn5mFXZ2y6afdHgm poxVjJti4SvDHAa6txxTBDdRL+a/davkgZWXxDMc3BUKCIGQ6280qe/diucudMw7tRP7 Ous9b3M1krtSjxSYmoivDmpQjg8tH+HApVr8L+r7+1iHtNjZhaPblaPULOYLDAxE4TYj /8ifPGBPNOUJe26JjFhYO3e9aJArSTqmIyqF3F5vr1vyjkGPd920A7k7bK2LJhPSMglA 894Q== X-Gm-Message-State: AOAM531exma9+ibPd4K08rbaCCyjpUBeKkHMyKyuYc2066wqP8Uhzsan ReVxX6tIJkpR9FItXQxvb2aKCi0HvSH1NwT6rjkN+bE5QL17 X-Google-Smtp-Source: ABdhPJwutBsiNFEqI0xG69qDeOD5jbbkDATr8/nzlp6Y/yl8JYFyWZWlDNQ7AKh2cGsfMelBkFyR9D2gvmAcOa80/TTAuD0d6ZIw MIME-Version: 1.0 X-Received: by 2002:a05:6638:1af:b0:32b:26b6:3a47 with SMTP id b15-20020a05663801af00b0032b26b63a47mr1993510jaq.233.1651122313718; Wed, 27 Apr 2022 22:05:13 -0700 (PDT) Date: Wed, 27 Apr 2022 22:05:13 -0700 In-Reply-To: <20220427230210.GA6837@lst.de> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000fd713505ddafde13@google.com> Subject: Re: [syzbot] general protection fault in btrfs_stop_all_workers From: syzbot To: clm@fb.com, dsterba@suse.com, hch@lst.de, josef@toxicpanda.com, linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, wqu@suse.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org Hello, syzbot has tested the proposed patch and the reproducer did not trigger any issue: Reported-and-tested-by: syzbot+a2c720e0f056114ea7c6@syzkaller.appspotmail.com Tested on: commit: ade4dbbb btrfs: don't call destroy_workqueue on NULL w.. git tree: git://git.infradead.org/users/hch/misc.git btrfs-workqueue-fix kernel config: https://syzkaller.appspot.com/x/.config?x=17dad21e0facb5e6 dashboard link: https://syzkaller.appspot.com/bug?extid=a2c720e0f056114ea7c6 compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 Note: no patches were applied. Note: testing is done by a robot and is best-effort only.