public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+f69bfae0a4eb29976e44@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	 wintera@linux.ibm.com
Subject: Re: [syzbot] [smc?] general protection fault in smc_diag_dump_proto
Date: Tue, 16 Dec 2025 10:46:02 -0800	[thread overview]
Message-ID: <6941a8ea.050a0220.dc18b.004f.GAE@google.com> (raw)
In-Reply-To: <f8c6a628-5626-4a8b-9636-d7aa38c89da0@linux.ibm.com>

Hello,

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

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

Tested on:

commit:         8f7aa3d3 Merge tag 'net-next-6.19' of git://git.kernel..
git tree:       net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10841d92580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4de27aef5cfef7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=f69bfae0a4eb29976e44
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=13eee77c580000

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

       reply	other threads:[~2025-12-16 18:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f8c6a628-5626-4a8b-9636-d7aa38c89da0@linux.ibm.com>
2025-12-16 18:46 ` syzbot [this message]
     [not found] <655fe7d5-3836-4ed8-98fd-05cf281d7a54@linux.ibm.com>
2025-12-17  9:32 ` [syzbot] [smc?] general protection fault in smc_diag_dump_proto syzbot
2024-08-09 16:27 [syzbot] [net?] [s390?] " syzbot
2025-12-07  4:29 ` [syzbot] [smc?] " syzbot
2025-12-17  9:39   ` Alexandra Winter

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=6941a8ea.050a0220.dc18b.004f.GAE@google.com \
    --to=syzbot+f69bfae0a4eb29976e44@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=wintera@linux.ibm.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