From: syzbot <syzbot+f69bfae0a4eb29976e44@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: Re: [syzbot] [smc?] general protection fault in smc_diag_dump_proto
Date: Tue, 16 Dec 2025 09:15:18 -0800 [thread overview]
Message-ID: <694193a6.a70a0220.25eec0.0000.GAE@google.com> (raw)
In-Reply-To: <000000000000fabef5061f429db7@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: [syzbot] [smc?] general protection fault in smc_diag_dump_proto
Author: wintera@linux.ibm.com
#syz test
--- a/net/smc/af_smc.c
+++ b/net/smc/af_smc.c
@@ -3524,6 +3524,9 @@ static int __init smc_init(void)
goto out_pernet_subsys_stat;
smc_clc_init();
+ INIT_HLIST_HEAD(&smc_v4_hashinfo.ht);
+ INIT_HLIST_HEAD(&smc_v6_hashinfo.ht);
+
rc = smc_nl_init();
if (rc)
goto out_ism;
@@ -3581,8 +3584,6 @@ static int __init smc_init(void)
pr_err("%s: sock_register fails with %d\n", __func__, rc);
goto out_proto6;
}
- INIT_HLIST_HEAD(&smc_v4_hashinfo.ht);
- INIT_HLIST_HEAD(&smc_v6_hashinfo.ht);
rc = smc_ib_register_client();
if (rc) {
next prev parent reply other threads:[~2025-12-16 17:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 16:27 [syzbot] [net?] [s390?] " syzbot
2024-08-12 9:28 ` [syzbot] " syzbot
2024-08-13 1:16 ` syzbot
2024-08-13 3:21 ` syzbot
2024-09-18 9:05 ` Jeongjun Park
2024-09-18 12:13 ` syzbot
2024-09-18 16:04 ` Jeongjun Park
2024-09-18 16:43 ` syzbot
2024-09-19 12:43 ` Jeongjun Park
2024-09-19 17:34 ` syzbot
2025-12-07 4:29 ` [syzbot] [smc?] " syzbot
2025-12-17 9:39 ` Alexandra Winter
2025-12-16 17:15 ` syzbot [this message]
2025-12-17 8:18 ` Forwarded: " syzbot
2025-12-22 9:50 ` Forwarded: Re: [PATCH net] net/smc: Initialize smc hashtables before registering users 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=694193a6.a70a0220.25eec0.0000.GAE@google.com \
--to=syzbot+f69bfae0a4eb29976e44@syzkaller.appspotmail.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
Powered by JetHome