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 42A0CEE499D for ; Fri, 18 Aug 2023 21:50:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241159AbjHRVuB (ORCPT ); Fri, 18 Aug 2023 17:50:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38436 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241126AbjHRVtc (ORCPT ); Fri, 18 Aug 2023 17:49:32 -0400 Received: from mail-pl1-f198.google.com (mail-pl1-f198.google.com [209.85.214.198]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8034A3C34 for ; Fri, 18 Aug 2023 14:49:31 -0700 (PDT) Received: by mail-pl1-f198.google.com with SMTP id d9443c01a7336-1bf0b05bbbeso20096105ad.0 for ; Fri, 18 Aug 2023 14:49:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692395371; x=1693000171; h=to:from:subject:message-id:in-reply-to:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=htaUE46w/jpYC6GT7fp3ZjxKV5A/VMyj18jALNrVscc=; b=AfyoeQ+v8eLAmECH9I0kDMGBoMI8WFNzk8iWuMdFuHj7Gq2AanxyAQezGy+tdsHsoC UB+UJbzB+tNTFLbmARVITzeR1ufXwycaJwlhzIfuT91DNS8GY7m+ghzyluME5gz1hPsh lb+NImdqSqlDVgSHWu+xnYbOMOLg9etapWzMXzvtbWWbiWV4p0K5Jf1Y1VmE1iqkrC3I bJeatElQXwq+6WasU2fDixCsYhhySbFRYk/BF++6FOyaU9bfwmHBnb8cnTVRCGzWSHTw AqDNlAzZVZev1MZxO15aU5pEOA4LLtY7zVvsfFRYf4i/GbPIm6V9RPCyWiZrdYtj/z+c TlCA== X-Gm-Message-State: AOJu0YzEZTanR2dMUeDg1ULMYxpl8Yn1h++wr14uLP/fYbbYAEFoG7E4 9P65Ij9a5JAqK5102kaiCAYAROm5Suen+9pyuZ9ZP9iKUUDI X-Google-Smtp-Source: AGHT+IEopbrZK9WaQ3DK9uOGyDRimniWVNSjuyIQEZW05tCpOq3HSBrweE8epEmU42rAUfq9ZdMzCGUXU4KTs7VqsrNiciOWveJa MIME-Version: 1.0 X-Received: by 2002:a17:903:22cd:b0:1b8:9533:65b0 with SMTP id y13-20020a17090322cd00b001b8953365b0mr131968plg.5.1692395371136; Fri, 18 Aug 2023 14:49:31 -0700 (PDT) Date: Fri, 18 Aug 2023 14:49:30 -0700 In-Reply-To: X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000ea8eaa0603398076@google.com> Subject: Re: [syzbot] [f2fs?] possible deadlock in f2fs_getxattr From: syzbot To: chao@kernel.org, jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net, 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-fsdevel@vger.kernel.org Hello, syzbot has tested the proposed patch and the reproducer did not trigger any issue: Reported-and-tested-by: syzbot+e5600587fa9cbf8e3826@syzkaller.appspotmail.com Tested on: commit: 47e4a92b f2fs: avoid false alarm of circular locking git tree: https://github.com/jaegeuk/f2fs.git g-dev-test console output: https://syzkaller.appspot.com/x/log.txt?x=16b569efa80000 kernel config: https://syzkaller.appspot.com/x/.config?x=6d0f369ef5fb88c9 dashboard link: https://syzkaller.appspot.com/bug?extid=e5600587fa9cbf8e3826 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 Note: no patches were applied. Note: testing is done by a robot and is best-effort only.