From: syzbot <syzbot+ccf1421545dbe5caa20c@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, ojaswin@linux.ibm.com,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: [syzbot] [ext4?] kernel BUG in ext4_es_cache_extent (4)
Date: Wed, 11 Feb 2026 02:03:02 -0800 [thread overview]
Message-ID: <698c53d6.050a0220.340abe.000c.GAE@google.com> (raw)
In-Reply-To: <aYw97hffWIoiQQGH@li-dc0c254c-257c-11b2-a85c-98b6c1322444.ibm.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+ccf1421545dbe5caa20c@syzkaller.appspotmail.com
Tested-by: syzbot+ccf1421545dbe5caa20c@syzkaller.appspotmail.com
Tested on:
commit: 4f5e8e6f et4: allow zeroout when doing written to unwr..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
console output: https://syzkaller.appspot.com/x/log.txt?x=17815b22580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a535ad5429f72a2
dashboard link: https://syzkaller.appspot.com/bug?extid=ccf1421545dbe5caa20c
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=120cccaa580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-02-11 10:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 2:08 [syzbot] [ext4?] kernel BUG in ext4_es_cache_extent (4) syzbot
2026-02-09 19:22 ` Ojaswin Mujoo
2026-02-09 19:42 ` syzbot
2026-02-10 5:49 ` Ojaswin Mujoo
2026-02-10 6:20 ` syzbot
2026-02-10 12:33 ` Ojaswin Mujoo
2026-02-10 15:24 ` syzbot
2026-02-10 18:06 ` Ojaswin Mujoo
2026-02-10 19:59 ` Ojaswin Mujoo
2026-02-10 20:54 ` syzbot
2026-02-11 8:29 ` Ojaswin Mujoo
2026-02-11 10:03 ` syzbot [this message]
2026-02-11 13:42 ` Ojaswin Mujoo
2026-02-11 16:44 ` syzbot
2026-03-03 19:19 ` syzbot
2026-03-12 17:45 ` Ojaswin Mujoo
2026-03-12 18:05 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=698c53d6.050a0220.340abe.000c.GAE@google.com \
--to=syzbot+ccf1421545dbe5caa20c@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox