From: syzbot <syzbot+b0a0670332b6b3230a0a@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] WARNING in __folio_mark_dirty (3)
Date: Thu, 04 Dec 2025 21:33:01 -0800 [thread overview]
Message-ID: <69326e8d.a70a0220.2ea503.00f2.GAE@google.com> (raw)
In-Reply-To: <20251205045415.1392139-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+b0a0670332b6b3230a0a@syzkaller.appspotmail.com
Tested-by: syzbot+b0a0670332b6b3230a0a@syzkaller.appspotmail.com
Tested on:
commit: 2061f18a Merge tag 'caps-pr-20251204' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1473b01a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8a99cdde3da055cf
dashboard link: https://syzkaller.appspot.com/bug?extid=b0a0670332b6b3230a0a
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=10bdb01a580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-12-05 5:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251205045415.1392139-1-kartikey406@gmail.com>
2025-12-05 5:33 ` syzbot [this message]
[not found] <20251121124101.332104-1-kartikey406@gmail.com>
2025-11-21 13:11 ` [syzbot] [ext4?] WARNING in __folio_mark_dirty (3) syzbot
[not found] <20251121115221.330869-1-kartikey406@gmail.com>
2025-11-21 12:34 ` syzbot
[not found] <20251121104426.329600-1-kartikey406@gmail.com>
2025-11-21 11:32 ` syzbot
[not found] <20251121013443.84021-1-kartikey406@gmail.com>
2025-11-21 8:51 ` syzbot
2025-11-20 16:41 syzbot
2025-11-21 18:11 ` Andrew Morton
2025-11-21 19:02 ` Matthew Wilcox
2025-11-21 19:14 ` Andrew Morton
2025-12-02 13:25 ` Theodore Tso
2025-12-02 13:47 ` 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=69326e8d.a70a0220.2ea503.00f2.GAE@google.com \
--to=syzbot+b0a0670332b6b3230a0a@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.