From: syzbot <syzbot+038b7bf43423e132b308@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, yi.zhang@huawei.com
Subject: Re: [syzbot] [ext4?] kernel BUG in ext4_es_cache_extent (3)
Date: Tue, 30 Sep 2025 02:37:05 -0700 [thread overview]
Message-ID: <68dba4c1.a70a0220.10c4b.0138.GAE@google.com> (raw)
In-Reply-To: <20250930091631.310211-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+038b7bf43423e132b308@syzkaller.appspotmail.com
Tested-by: syzbot+038b7bf43423e132b308@syzkaller.appspotmail.com
Tested on:
commit: 30d4efb2 Merge tag 'for-linus-6.18-rc1-tag' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16b3f27c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=607d55e4510cba63
dashboard link: https://syzkaller.appspot.com/bug?extid=038b7bf43423e132b308
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=13cb16e2580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-09-30 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250930091631.310211-1-kartikey406@gmail.com>
2025-09-30 9:37 ` syzbot [this message]
[not found] <20250930104454.313735-1-kartikey406@gmail.com>
2025-09-30 11:22 ` syzbot
[not found] <20250929144049.359092-1-kartikey406@gmail.com>
2025-09-29 15:01 ` syzbot
[not found] <20250928094135.11584-1-kartikey406@gmail.com>
2025-09-28 10:02 ` syzbot
[not found] <20250928091137.9626-1-kartikey406@gmail.com>
2025-09-28 9:26 ` syzbot
[not found] <20250928074511.6263-1-kartikey406@gmail.com>
2025-09-28 8:00 ` syzbot
2025-09-04 9:44 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=68dba4c1.a70a0220.10c4b.0138.GAE@google.com \
--to=syzbot+038b7bf43423e132b308@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yi.zhang@huawei.com \
/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
all inboxes | Powered by JetHome®