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 F34201C6BD for ; Fri, 3 May 2024 03:44:19 +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=1714707861; cv=none; b=Lo6E65zDbVCXG4FfsCMmF9Or4Oko2QxZIl2alrb07P5MvGpChxKLEDPBu3YcEHd7sZeEw+ZwBoRQHHb5J70IJHSfLoPqpqx9GV5yGWH0nPFqwOj8MSkgeXkfh/htjbetsYcJNQZ9UAREJ8BBEhJh9FlFcfG0YVm5JLNnk6PjHNY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1714707861; c=relaxed/simple; bh=DC68Fan9U1mDvvm9HS7/KL5cq/tCfXtYDl7pvERFoFo=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To: Content-Type; b=fz7TT3H7DSvBTLyl1OYZpfcRZZ3hzzBpVlW4roVRoje1uk2lRtPZmYVbfMJJI+upsiGWM0gBV7R7nfw8RjGIPi3LWpFZEyX4D3bLXRPAoLk5BHbhGeUqw47BM0yPFArNZUw6m8V9NMqIaEF5n2NMIdMnZOq9WONzjcbR6bowQmA= 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-7da41c44da7so1000165939f.0 for ; Thu, 02 May 2024 20:44:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714707859; x=1715312659; 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=vLQgH9W0nu0jnZCYrl1BWQHy/FQAaZBjdsB+l5PgaasjOPBVyNz5F67C6mt4lNofHc 079vBlrhXPVHri6OXYsqMkhMn0MOvOUyRmhnqIud7g4dH9ZrqU3TdyIGjWY/pRGztUCd G4MEWWGZbfAAxZN82+lAtpmiYPi1FsoOm3PuIOzfO/Abff+ZgTofLrxdAa3iVqJQZYH2 dgFz/8CGAvPUKNxFXohNVKbqdxGf3NEcF2QqV2jB44NSYDmx34FO5OTYKEpr50zrQug5 LOJprJGMWuM+KjsVtvCUTK6ZlQB6xZI4LcHgOG+k+IEqIeIZkqz8ygCjFJQCyLrrprsZ gMBQ== X-Forwarded-Encrypted: i=1; AJvYcCVpJzGVlP5HkBD9f0YZJTULCrHyNMnj85yqJVG453PmaYtmwXDoyjPEaHCJ/OhpJCM6HUyhWlxn+EWfA1/leUda5+4k7DLqOqec1JAk X-Gm-Message-State: AOJu0Ywu/6Q1i6sQTkuGxsB8yZzv84CVrBFM2ZwDVC6d4QDZSrIF7N51 z+51o/IO99h7S1/p69X4dt9IctnvVkpABCHRikKlrzlgg8hQmB0ZXvWds51v0/A3BVYDgmpjcSj pavcxXcnSGcE9qMwtS3Mknp+wKjdIDONGgGdXdw07OfgjLpSJbSgKXDI= X-Google-Smtp-Source: AGHT+IF6jdtVimKJ3sPtIlW6psc1aZK/nSNQxAxNcKk6WGV4mZGOrwytWBePLmVCVM24GexqMQgZkn/SIF5cdqAA9s2wWfiSdIMn Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6638:3f0f:b0:487:5b21:e66f with SMTP id ck15-20020a0566383f0f00b004875b21e66fmr65625jab.0.1714707859267; Thu, 02 May 2024 20:44:19 -0700 (PDT) Date: Thu, 02 May 2024 20:44:19 -0700 In-Reply-To: <000000000000dfd6a105f71001d7@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000d873390617848870@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 9 trees can be found at https://syzkaller.appspot.com/upstream/repos