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 060FDC433FE for ; Mon, 7 Nov 2022 12:37:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232271AbiKGMhd (ORCPT ); Mon, 7 Nov 2022 07:37:33 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60118 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232105AbiKGMha (ORCPT ); Mon, 7 Nov 2022 07:37:30 -0500 Received: from mail-il1-f200.google.com (mail-il1-f200.google.com [209.85.166.200]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 565BB1B9FE for ; Mon, 7 Nov 2022 04:37:29 -0800 (PST) Received: by mail-il1-f200.google.com with SMTP id o10-20020a056e02102a00b003006328df7bso8485760ilj.17 for ; Mon, 07 Nov 2022 04:37:29 -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:in-reply-to:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=G4j4i1D9g/K0Cayton2okA3A9p6eYtwnuNOgUF/2ByQ=; b=ameRHsJZx5o8bAybe9+81RRaa1AvP7l7YuRc49addn5IL8T4aFBlmbLq1OPVct9kBf soUyAHZSKdNWMXwPGis0WfZuz8A/XTJMXtnP0kdgeIBCjIETzKfbpmSyxZUMUuoJNzbx 72DWeCCRQlEzQKRnydNtbElDD+trmROCiK45RwO3zDOCQ6rRVS5OFtzDJIJBLqXq/a0n HBYzHKmvgfDKVpfcT+0FDBjqx+5ByQZpena3+jHuHdqlAIajeEKY0IBM7aoyU84+YTd4 7BVsxXnuT4ctqccKZ2avaTwPoahajtjqcmqVTUEpj36mJorM3eFH1y3aIYxVy8jVGcli fdqw== X-Gm-Message-State: ACrzQf1N9EEifrNjtw7SHrmvGXelCEEPYGkvy8lOI+E3u/qZAuFyCIDE e53lUjbrz0GCuOSQZTNvyecMx4ujcyEGdxRIQsZG5aaH9LeY X-Google-Smtp-Source: AMsMyM7hL2RBAgD8t+s2gyQ+GiR0UO0q3NHbLXrJlSmqrZh6R4WmKFa8dNIEZN8EXbW1Ib8B16CXhBZMKKoRRN9U5sAUb6W/TsYn MIME-Version: 1.0 X-Received: by 2002:a05:6602:1586:b0:6d8:22c5:102a with SMTP id e6-20020a056602158600b006d822c5102amr9042086iow.156.1667824648749; Mon, 07 Nov 2022 04:37:28 -0800 (PST) Date: Mon, 07 Nov 2022 04:37:28 -0800 In-Reply-To: <000000000000c3a53d05de992007@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000bc92bf05ece0af6f@google.com> Subject: Re: kernel BUG in ext4_writepages From: syzbot To: gregkh@linuxfoundation.org, jack@suse.cz, lczerner@redhat.com, linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, stable-commits@vger.kernel.org, stable@kernel.org, stable@vger.kernel.org, syzkaller-android-bugs@googlegroups.com, tadeusz.struk@linaro.org, tytso@mit.edu Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org This bug is marked as fixed by commit: ext4: Avoid crash when inline data creation follows DIO write But I can't find it in any tested tree for more than 90 days. Is it a correct commit? Please update it by replying: #syz fix: exact-commit-title Until then the bug is still considered open and new crashes with the same signature are ignored.