From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-io1-f69.google.com (mail-io1-f69.google.com [209.85.166.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id EC27F1B94F for ; Fri, 28 Jun 2024 03:48:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.166.69 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1719546493; cv=none; b=uhrK36Gu10+3Jv2feHexyTgD2vTlKaLxjqNOPc1DToU296IJFpL4zkmDbjKGWkNNEbNVh+P2XqabO0/rKv/PWthwV6QjM35v/ENFf/jhR2/xoxrex3d1eCP9Z3BQGn5yj+hARu010Fe69mA3nPd7//rhrr61rggPi1/fXys1U9c= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1719546493; c=relaxed/simple; bh=4rfaUAidddvblASjtkMKjWyJL/CQTzUgNAb30NvOGhU=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To: Content-Type; b=l9Mx+T2AP6txNPfOfH2ixvj5ElgQHLL0WtlWDiDRZjpcEFtbFa4qf5yt3Vc1dTXe1UwVuSy6VfZTmb+aYlapM6HRLBwefcaJVB2+LabaullmOOXy+vtpzQIGSWTN6W4oRnXLA2QKUw0cRNFr6+gc15ZX5UbIns0+FxXOSVBfLTE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.166.69 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-io1-f69.google.com with SMTP id ca18e2360f4ac-7f61f4c998bso22337039f.1 for ; Thu, 27 Jun 2024 20:48:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719546491; x=1720151291; 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=4rfaUAidddvblASjtkMKjWyJL/CQTzUgNAb30NvOGhU=; b=TSu6T6QlXiZ3FEgLdFJJHJBwYEINqVgzclwPmG4xXC3daWcBevJXa5H2AjUG0zyx+Y PptILOnwqsYTU8iMxpJwKZpFi3PpuHnVC69JRVTqHIs/WxDx1wUvZ0VM+33zF+5AjDB8 mxB1sUfHHiJnyRUyFuHiG2ZlbOura1gH4G7eik8D0IK8hlnQD24BVdStW0LTEPANJSHE R4mhEWRFNjY+XHkSPOAnbj7W0kAnKdc/rTk9I73u5CEHwVYUWq3I3uqqj2fpmP1pXvwI TSyE8znkDTajGRu3E4RFrjBecFT913wMViD/Vdc+hGmlq4YTt6Jitva1AyTJUaj7w7Gv x04Q== X-Forwarded-Encrypted: i=1; AJvYcCUp1An4xo6rRE0Y39O8Dpg/N57lnI0d0w041BzNaD60u6SfwKvKuEtv9xSSuB4Vwu000qSJKuXi6n7IFHOPDM36lJbnJEjeOlKTow== X-Gm-Message-State: AOJu0Yw7JZH/CCnjEYVWoawvlV3L3NGVwX+guJwiNRq98ZUj7KzPqbhs 2+Oum7vhHS8+3oobyY3zpjCv6+o8IbeMM6zIMHywPev5p+DkWRbRe1Crbtme0BmwIwo9yJpNmxY 3rfxfwV0WB5FdzDpSobC8rV3TBkUEblYKKcH2MCdU+zdhL4Er0yBUs6k= X-Google-Smtp-Source: AGHT+IEBBqgISQtup2Pw/1uKpqjKjFEX4D7SLDczK0UdOyHzAXI7q0Lb5rMjDMzvhSNoR5lytn2LnreFrukLoL+dlECHsYSSKav0 Precedence: bulk X-Mailing-List: linux-ext4@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6638:9611:b0:4b9:bdfd:f15b with SMTP id 8926c6da1cb9f-4b9ece1ba70mr1423229173.4.1719546491126; Thu, 27 Jun 2024 20:48:11 -0700 (PDT) Date: Thu, 27 Jun 2024 20:48:11 -0700 In-Reply-To: <000000000000dfd6a105f71001d7@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000c7587c061beb1db5@google.com> Subject: Re: [syzbot] kernel BUG in ext4_write_inline_data From: syzbot To: adilger.kernel@dilger.ca, eadavis@qq.com, 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" 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 10 trees can be found at https://syzkaller.appspot.com/upstream/repos