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 048FEEE4993 for ; Sun, 20 Aug 2023 18:41:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231641AbjHTSl4 (ORCPT ); Sun, 20 Aug 2023 14:41:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59580 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231609AbjHTSlx (ORCPT ); Sun, 20 Aug 2023 14:41:53 -0400 Received: from mail-pl1-f200.google.com (mail-pl1-f200.google.com [209.85.214.200]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4468C1BCF for ; Sun, 20 Aug 2023 11:41:24 -0700 (PDT) Received: by mail-pl1-f200.google.com with SMTP id d9443c01a7336-1bf707f526bso6321075ad.1 for ; Sun, 20 Aug 2023 11:41:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692556884; x=1693161684; 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=F/n5kjMvYzdRUXwH8feZ+4YEm3skk2x5QaWimKw+DCM=; b=FQGIRDSXTTPb0SeNWR4bA9dStgXGmkQBOZFEOUIogfOsG10uQaowhCmUR5A6IAytFb 9sALnn0FKzKa6UcwdsP32bTcSHyonInv+ciyD2f9gT1UJTj1qZyp0BtruMSGbM+i0FwV 4QmAwUYZLcsMHvoXpnrlS7UuHlm5oXWXP8mmRnpG/Q+fjEE4b4dHureBvsK1RchxV/of Fzvj+ZcY8mlpiCZ4vDcasFInF5HJgM9XWUClor73xnbD76lVf7Bj6e3ZiKT/xeScpzBV oDu1llZxHfno8C78UEHB0X0O3u1iFaDRiROULWF2druoV6t5oNm8eMaDPyFcpyscF4Z9 7BLQ== X-Gm-Message-State: AOJu0YwXK+gM4Or+KsB7OBLq+XiUOivfmFjGKRMEqsLbi1nIbusdsugH JQQG/sJlAhbMnZfkDU+snJgyY3tIbEEkSgzaAgNg6wKhfPna X-Google-Smtp-Source: AGHT+IG3eaeUAH2EW45k/+HZjIXX99Q9piV7GARJu71AM1i236ME0RtbJCZz+N43b2fgb4vOTwTGQxFuzEj7n5oY0lhEjCqFkOik MIME-Version: 1.0 X-Received: by 2002:a17:902:c449:b0:1bb:b74c:88fa with SMTP id m9-20020a170902c44900b001bbb74c88famr1918271plm.6.1692556883825; Sun, 20 Aug 2023 11:41:23 -0700 (PDT) Date: Sun, 20 Aug 2023 11:41:23 -0700 In-Reply-To: <000000000000dc83d605f0c70a11@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000d299b406035f1bbd@google.com> Subject: Re: [syzbot] [nilfs?] kernel BUG in folio_end_writeback From: syzbot To: akpm@linux-foundation.org, brauner@kernel.org, konishi.ryusuke@gmail.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-nilfs@vger.kernel.org, syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk, willy@infradead.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org syzbot suspects this issue was fixed by commit: commit 92c5d1b860e9581d64baca76779576c0ab0d943d Author: Ryusuke Konishi Date: Fri May 26 02:13:32 2023 +0000 nilfs2: reject devices with insufficient block count bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=170c6337a80000 start commit: 929ed21dfdb6 Merge tag '6.4-rc4-smb3-client-fixes' of git:.. git tree: upstream kernel config: https://syzkaller.appspot.com/x/.config?x=3da6c5d3e0a6c932 dashboard link: https://syzkaller.appspot.com/bug?extid=7e5cf1d80677ec185e63 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16cb3b69280000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10f34201280000 If the result looks correct, please mark the issue as fixed by replying with: #syz fix: nilfs2: reject devices with insufficient block count For information about bisection process see: https://goo.gl/tpsmEJ#bisection