From: syzbot <syzbot+4d55dad3a9e8e9f7d2b5@syzkaller.appspotmail.com>
To: dmantipov@yandex.ru, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] KASAN: use-after-free Read in __ocfs2_flush_truncate_log
Date: Fri, 24 Oct 2025 06:39:04 -0700 [thread overview]
Message-ID: <68fb8178.050a0220.346f24.00ed.GAE@google.com> (raw)
In-Reply-To: <20251024071530.lavdB%dmantipov@yandex.ru>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+4d55dad3a9e8e9f7d2b5@syzkaller.appspotmail.com
Tested-by: syzbot+4d55dad3a9e8e9f7d2b5@syzkaller.appspotmail.com
Tested on:
commit: 4fc43deb Linux 6.12.55
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git linux-6.12.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16b98258580000
kernel config: https://syzkaller.appspot.com/x/.config?x=fefde68860cfc8b6
dashboard link: https://syzkaller.appspot.com/bug?extid=4d55dad3a9e8e9f7d2b5
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=12ad6d42580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-10-24 13:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251024071530.lavdB%dmantipov@yandex.ru>
2025-10-24 13:39 ` syzbot [this message]
[not found] <20251029062739.WT_1W%dmantipov@yandex.ru>
2025-10-29 15:25 ` [syzbot] [ocfs2?] KASAN: use-after-free Read in __ocfs2_flush_truncate_log syzbot
[not found] <20251029062544.q4Amh%dmantipov@yandex.ru>
2025-10-29 12:43 ` syzbot
[not found] <20251029062151.Gq0gL%dmantipov@yandex.ru>
2025-10-29 8:02 ` syzbot
[not found] <20251028182247.yvNrt%dmantipov@yandex.ru>
2025-10-28 21:28 ` syzbot
[not found] <20251028182010.VCEv_%dmantipov@yandex.ru>
2025-10-28 20:43 ` syzbot
[not found] <20251028181930.boW79%dmantipov@yandex.ru>
2025-10-28 18:27 ` syzbot
[not found] <20251028104156.MqXWB%dmantipov@yandex.ru>
2025-10-28 10:47 ` syzbot
[not found] <20251028104117.Q0izB%dmantipov@yandex.ru>
2025-10-28 10:45 ` syzbot
[not found] <20251028104003.OE-Gy%dmantipov@yandex.ru>
2025-10-28 10:41 ` syzbot
[not found] <20251024071518.x1MIZ%dmantipov@yandex.ru>
2025-10-24 12:20 ` syzbot
[not found] <20251024071151.6PBhO%dmantipov@yandex.ru>
2025-10-24 7:48 ` syzbot
[not found] <20251022121354.-oB1f%dmantipov@yandex.ru>
2025-10-22 13:01 ` syzbot
[not found] <068e55cc-f5c0-42ad-99b5-352830583144@yandex.ru>
2025-10-22 10:50 ` syzbot
[not found] <a9cfa569-b234-4ad0-b2e5-1a227e7ea9ac@yandex.ru>
2025-10-20 11:11 ` syzbot
[not found] <cbd65371-547c-4644-9e68-9958e348e9ec@yandex.ru>
2025-10-20 10:50 ` syzbot
2024-09-29 4:47 Lizhi Xu
2024-09-29 5:09 ` [syzbot] " syzbot
-- strict thread matches above, loose matches on Subject: below --
2024-09-28 20: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=68fb8178.050a0220.346f24.00ed.GAE@google.com \
--to=syzbot+4d55dad3a9e8e9f7d2b5@syzkaller.appspotmail.com \
--cc=dmantipov@yandex.ru \
--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.