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 B55E4C433FE for ; Thu, 20 Oct 2022 16:32:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229970AbiJTQcj (ORCPT ); Thu, 20 Oct 2022 12:32:39 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59364 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230156AbiJTQcd (ORCPT ); Thu, 20 Oct 2022 12:32:33 -0400 Received: from mail-il1-f197.google.com (mail-il1-f197.google.com [209.85.166.197]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8C17D1AA26B for ; Thu, 20 Oct 2022 09:32:32 -0700 (PDT) Received: by mail-il1-f197.google.com with SMTP id s2-20020a056e02216200b002f9de38e484so305270ilv.8 for ; Thu, 20 Oct 2022 09:32:32 -0700 (PDT) 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=UKNN3axs1y811QkhsVcYtMf113asLOYvCITq8yCsIOI=; b=GM0KQTjVZx7ceSAEtnHUBubynHqVdg6MeqVqxRqBrThdhqfNLyevdh5H8Avbi+OZFw N/qo5U9jw7jSprijw7afTOYma7BlAVIfEs1AhxDgKt2yOpsHv/6TcqnFgy6G3O4ypkvH HoQJU5Bd4pjPuNDArr4MBRZS3Z8jV+nsipOhrE8R1nnr2XXpmcUtIg3DAaEJZsf5QWxt Lwfr86r4l/kL04rkIWbkcfXqCNL/LAN8WbLtu2sQY9Q81sh3S/re4g0/ZPGlQt2tlw6m 0snXywtBBLk0eLlifdBNzjGLO8mNfLlQqYLy5Rfg5ChTxowheApqqaJ8jJ87buzrn8y9 vBYg== X-Gm-Message-State: ACrzQf2XA4lEPGjBc2MtECXgl06C3ZBVdcE1fkTt8dAcYGRpodJ4d3b0 q+YNantmCJlbj+skXfnJcot1blFrA0f3+rZa9fRFLXHe2Dzr X-Google-Smtp-Source: AMsMyM4FPk0iRiokf85qWc1ZXECTEgMCQq+Q8VRal+EfXVpDu+LSoILYcUwg/tzPl125RD3+HZ/hveGyU+kyJ/AQ4rT8VBRuhcH/ MIME-Version: 1.0 X-Received: by 2002:a05:6e02:2164:b0:2fa:e426:dc5e with SMTP id s4-20020a056e02216400b002fae426dc5emr10321935ilv.213.1666283551925; Thu, 20 Oct 2022 09:32:31 -0700 (PDT) Date: Thu, 20 Oct 2022 09:32:31 -0700 In-Reply-To: <0000000000006c411605e2f127e5@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000352cf605eb79dfde@google.com> Subject: Re: kernel BUG in ext4_free_blocks (2) From: syzbot To: adilger.kernel@dilger.ca, gregkh@linuxfoundation.org, lczerner@redhat.com, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, sashal@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-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 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.