From: syzbot <syzbot+eec8f2693d71386bd600@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] INFO: trying to register non-static key in f2fs_exist_written_data
Date: Fri, 08 May 2026 19:45:01 -0700 [thread overview]
Message-ID: <69fe9fad.170a0220.39e8c4.0004.GAE@google.com> (raw)
In-Reply-To: <20260509010515.84065-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+eec8f2693d71386bd600@syzkaller.appspotmail.com
Tested-by: syzbot+eec8f2693d71386bd600@syzkaller.appspotmail.com
Tested on:
commit: e98d21c1 Add linux-next specific files for 20260508
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=155571ce580000
kernel config: https://syzkaller.appspot.com/x/.config?x=76d40e8423bfbf00
dashboard link: https://syzkaller.appspot.com/bug?extid=eec8f2693d71386bd600
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=11f783ce580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2026-05-09 2:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260509010515.84065-1-kartikey406@gmail.com>
2026-05-09 2:45 ` syzbot [this message]
[not found] <20260509010702.84144-1-kartikey406@gmail.com>
2026-05-09 2:33 ` [syzbot] [f2fs?] INFO: trying to register non-static key in f2fs_exist_written_data syzbot
2026-05-08 23:03 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=69fe9fad.170a0220.39e8c4.0004.GAE@google.com \
--to=syzbot+eec8f2693d71386bd600@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.