From: syzbot <syzbot+24d8b70f039151f65590@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nilfs?] WARNING: ODEBUG bug in nilfs_detach_log_writer (2)
Date: Tue, 28 Oct 2025 21:24:03 -0700 [thread overview]
Message-ID: <690196e3.050a0220.32483.01e7.GAE@google.com> (raw)
In-Reply-To: <tencent_EFA7FBC6CC92D88645C98F6EEB2EC04C8706@qq.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+24d8b70f039151f65590@syzkaller.appspotmail.com
Tested-by: syzbot+24d8b70f039151f65590@syzkaller.appspotmail.com
Tested on:
commit: b98c94ee arm64: mte: Do not warn if the page is alread..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=11a09c92580000
kernel config: https://syzkaller.appspot.com/x/.config?x=158bd6857eb7a550
dashboard link: https://syzkaller.appspot.com/bug?extid=24d8b70f039151f65590
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=128b8fe2580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-10-29 4:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 21:18 [syzbot] [nilfs?] WARNING: ODEBUG bug in nilfs_detach_log_writer (2) syzbot
2025-10-27 22:17 ` Ryusuke Konishi
2025-10-28 3:26 ` Edward Adam Davis
2025-10-28 4:07 ` syzbot
2025-10-28 5:16 ` Edward Adam Davis
2025-10-28 6:54 ` syzbot
2025-10-28 7:45 ` Edward Adam Davis
2025-10-28 8:09 ` syzbot
2025-10-29 3:06 ` Edward Adam Davis
2025-10-29 4:24 ` syzbot [this message]
2025-10-29 5:23 ` [PATCH] nilfs2: Avoid having an active sc_timer before freeing sci Edward Adam Davis
2025-10-29 10:17 ` Ryusuke Konishi
2025-10-29 22:51 ` Ryusuke Konishi
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=690196e3.050a0220.32483.01e7.GAE@google.com \
--to=syzbot+24d8b70f039151f65590@syzkaller.appspotmail.com \
--cc=eadavis@qq.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox