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 61099C64ED6 for ; Wed, 1 Mar 2023 12:46:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229826AbjCAMql (ORCPT ); Wed, 1 Mar 2023 07:46:41 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49422 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229486AbjCAMql (ORCPT ); Wed, 1 Mar 2023 07:46:41 -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 74A95302BE for ; Wed, 1 Mar 2023 04:46:40 -0800 (PST) Received: by mail-il1-f200.google.com with SMTP id h12-20020a92c08c000000b00316f82f1d98so7673969ile.7 for ; Wed, 01 Mar 2023 04:46:40 -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=V5gRBWvCrC4ivORDLYanYAKruxMNDrxF3nhXlCgZ6d4=; b=D78Z4q5VHLIJy1lBlyzyS2PNK7XkW0fNg1WTNz7lFw5xnAYoYjfsEbpgbnXJKRUUaw G3kYk1aIXNL/Nrar3oKgVA1HLeviTknluBECzpyEbK4oMNtMe0jp/SEqfNm9cI1FhmfS A+gqdQLLd/LDTFarnXALjxajIdvesVd+agHiP09+uzuks4NZtn/lQZ8U87+JdQk+yVgv eJf/H8gVyOFHX9Kzzdx38aib6fEGrVz0hbj9ZjHWdfU1LBknsAR5kGNHUD42TKKRFn2u hKsz6j5renH9UKTE2dWIjBJVyGCbue18Dgr6mwZno2q262Z3D5cO/5efIYTnbB5AKCRq Ymgw== X-Gm-Message-State: AO0yUKWn/Ah1xoSV2kB/wVfQwRByD50nffTr4jpjXzEQ13eEZYqx/lMK tAoxglJbGUGMz03htFVRdVtkGw+BEKZktkr1eIH7/gOONod+ X-Google-Smtp-Source: AK7set+jinAjUAWYrdG6kv0VrfxDnBTCXLpXXJuHSxiCG5jjotaU+gO2m6Gn4BjUeDtSSYYxYS1qjF7hYGwhrzXiIgt3sUFd+X2Y MIME-Version: 1.0 X-Received: by 2002:a92:ae12:0:b0:310:d348:e59b with SMTP id s18-20020a92ae12000000b00310d348e59bmr2898095ilh.4.1677674799832; Wed, 01 Mar 2023 04:46:39 -0800 (PST) Date: Wed, 01 Mar 2023 04:46:39 -0800 In-Reply-To: <0000000000006c411605e2f127e5@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000007e24fb05f5d61afb@google.com> Subject: Re: [Android 5.10] kernel BUG in ext4_free_blocks (2) From: syzbot To: adilger.kernel@dilger.ca, gregkh@linuxfoundation.org, joneslee@google.com, lczerner@redhat.com, lee@kernel.org, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, nogikh@google.com, sashal@kernel.org, stable@vger.kernel.org, syzkaller-android-bugs@googlegroups.com, tadeusz.struk@linaro.org, tudor.ambarus@linaro.org, tytso@mit.edu Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org This bug is marked as fixed by commit: ext4: block range must be validated before use in ext4_mb_clear_bb() But I can't find it in the tested trees[1] 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. Kernel: Android 5.10 Dashboard link: https://syzkaller.appspot.com/bug?extid=15cd994e273307bf5cfa --- [1] I expect the commit to be present in: 1. android12-5.10-lts branch of https://android.googlesource.com/kernel/common