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 47AAECDB47E for ; Wed, 18 Oct 2023 08:48:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229741AbjJRIsq (ORCPT ); Wed, 18 Oct 2023 04:48:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37444 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230024AbjJRIsp (ORCPT ); Wed, 18 Oct 2023 04:48:45 -0400 Received: from mail-oa1-f70.google.com (mail-oa1-f70.google.com [209.85.160.70]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 51007C6 for ; Wed, 18 Oct 2023 01:48:43 -0700 (PDT) Received: by mail-oa1-f70.google.com with SMTP id 586e51a60fabf-1e990f0629cso8881655fac.2 for ; Wed, 18 Oct 2023 01:48:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697618922; x=1698223722; 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=DC68Fan9U1mDvvm9HS7/KL5cq/tCfXtYDl7pvERFoFo=; b=RSqRFD1fNdznRjg0Sr+do0lm7J3z4zt/wEEX/TsNRGyK6n7HIxz+dQkyxuq6g9uhD6 TNsmguN2FyRo4dEoikYopebggM+LQBcvttnNS9PX1DsD74nBAlqRnUZhZNwsuNeL0f50 8Ex1Uy0VkgzTX2Mwvk/VKxIZUJ6aCv1wPZKdgYP4RRmnGNo7GsK/K3+H6uDyokBhZehy d+eqTEvi4NUW/ycVTazrIOMviEi2Ceyh8lEsIpGcZ2BI0tHRJ5ZE9SmRFf3Latu4WYPR IpCGd+sKFxZtSufwWnBE5YKFbinxXHpLnJUKjQN/RYte/1L2+uXvY7DHjK+Zxesm37OI MvDw== X-Gm-Message-State: AOJu0Yxux4zSE0GZOu/c11nB4+JjGSTrVv5UkYqC7ZTCxhM/dRFDiWlS 5a2zbYvV7fKcmLgXuB0Dve4STvvNyJrZ4nK/IHsPfR4ghCmw X-Google-Smtp-Source: AGHT+IH5KX39Zu5WRNgK3VKyydT+0tvTjeetKkwDFus95ScBRPsXK3zjjJxvbV/6vxL20IQCDEZ9FHkNsLjuYTS+6mTaNsskXrjM MIME-Version: 1.0 X-Received: by 2002:a05:6870:3046:b0:1e9:dabc:9d6 with SMTP id u6-20020a056870304600b001e9dabc09d6mr2212109oau.1.1697618922448; Wed, 18 Oct 2023 01:48:42 -0700 (PDT) Date: Wed, 18 Oct 2023 01:48:42 -0700 In-Reply-To: <000000000000dfd6a105f71001d7@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000d62e9e0607f9b415@google.com> Subject: Re: [syzbot] kernel BUG in ext4_write_inline_data From: syzbot To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, nogikh@google.com, syzkaller-bugs@googlegroups.com, 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: fix race condition between buffer write and page_mkwrite 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: Linux Dashboard link: https://syzkaller.appspot.com/bug?extid=f4582777a19ec422b517 --- [1] I expect the commit to be present in: 1. for-kernelci branch of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git 2. master branch of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git 3. master branch of git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git 4. main branch of git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git The full list of 9 trees can be found at https://syzkaller.appspot.com/upstream/repos