mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+bdeb22a4b9a09ab9aa45@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] INFO: trying to register non-static key in ntfs_set_size
Date: Mon, 15 Sep 2025 21:01:06 -0700	[thread overview]
Message-ID: <68c8e102.050a0220.3c6139.0d27.GAE@google.com> (raw)
In-Reply-To: <tencent_9F73836FE96783BC44575767376BC6CFB305@qq.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+bdeb22a4b9a09ab9aa45@syzkaller.appspotmail.com
Tested-by: syzbot+bdeb22a4b9a09ab9aa45@syzkaller.appspotmail.com

Tested on:

commit:         c3067c2c Add linux-next specific files for 20250915
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1605fb62580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e269dbc7717119a2
dashboard link: https://syzkaller.appspot.com/bug?extid=bdeb22a4b9a09ab9aa45
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=104b8e42580000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2025-09-16  4:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-15 18:17 syzbot
2025-09-16  3:33 ` Edward Adam Davis
2025-09-16  4:01   ` syzbot [this message]
2025-09-16  3:48 ` Tetsuo Handa
2025-09-20  9:42   ` Tetsuo Handa
2025-10-04 10:43     ` Tetsuo Handa
2025-09-16  5:50 ` [PATCH Next] ntfs3: init run lock for extend inode Edward Adam Davis
2025-11-20  9:02   ` Konstantin Komarov

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=68c8e102.050a0220.3c6139.0d27.GAE@google.com \
    --to=syzbot+bdeb22a4b9a09ab9aa45@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

all inboxes | Powered by JetHome®