[moderation/CI] Re: net/smc: convert getsockopt to getsockopt_iter

syzbot ci has tested the following series

[v1] net/smc: convert getsockopt to getsockopt_iter
https://lore.kernel.org/all/[email protected]
* [PATCH net-next 1/2] smc: convert to getsockopt_iter
* [PATCH net-next 2/2] selftests: net: add SMC getsockopt_iter conversion test

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/4ed2003b-e2aa-49b1-ae79-ee6e68a28a4e

***

kernel build error

tree:      net-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base:      6a5d837f0ce2486383259b13d3c9c294c87add3b
arch:      amd64
compiler:  Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config:    https://ci.syzbot.org/builds/db5460d6-f612-4fda-a6d1-380f920b4c29/config

net/smc/af_smc.c:3186:45: error: no member named 'optlen_user' in 'struct sockopt'
net/smc/af_smc.c:3201:34: error: no member named 'optlen_user' in 'struct sockopt'
net/smc/af_smc.c:3207:33: error: no member named 'optlen_user' in 'struct sockopt'

***

If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
  Tested-by: [email protected]

---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at [email protected].

To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).

The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.

The email will later be sent to:
[[email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]]

If the report looks fine to you, reply with:
#syz upstream

If the report is a false positive, reply with
#syz invalid