From: syzbot <syzbot+3bfd2cc059ab93efcdb4@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com, eadavis@qq.com,
linux-kernel@vger.kernel.org, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] INFO: trying to register non-static key in mark_as_free_ex
Date: Tue, 03 Sep 2024 19:55:01 -0700 [thread overview]
Message-ID: <000000000000e1acf50621424c79@google.com> (raw)
In-Reply-To: <tencent_A84BB764577146D01363A3640961A3B06405@qq.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+3bfd2cc059ab93efcdb4@syzkaller.appspotmail.com
Tested-by: syzbot+3bfd2cc059ab93efcdb4@syzkaller.appspotmail.com
Tested on:
commit: 88fac175 Merge tag 'fuse-fixes-6.11-rc7' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1587c0b3980000
kernel config: https://syzkaller.appspot.com/x/.config?x=660f6eb11f9c7dc5
dashboard link: https://syzkaller.appspot.com/bug?extid=3bfd2cc059ab93efcdb4
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1277c88b980000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-09-04 2:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 1:15 [syzbot] [ntfs3?] INFO: trying to register non-static key in mark_as_free_ex syzbot
2024-09-04 2:28 ` Edward Adam Davis
2024-09-04 2:55 ` syzbot [this message]
2024-09-07 1:42 ` [PATCH] fs/ntfs3: Move condition bitmap.sb to before run_unpack Edward Adam Davis
2024-09-09 15:13 ` [syzbot] possible fix (linux-ntfs3) syzbot
[not found] <20240909151305.7057-1-almaz.alexandrovich@paragon-software.com>
2024-09-09 16:34 ` [syzbot] [ntfs3?] INFO: trying to register non-static key in mark_as_free_ex 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=000000000000e1acf50621424c79@google.com \
--to=syzbot+3bfd2cc059ab93efcdb4@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=eadavis@qq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--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