From: kernel test robot <lkp@intel.com>
To: Kees Cook <kees@kernel.org>, Jakub Kicinski <kuba@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Kees Cook <kees@kernel.org>, Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Kuniyuki Iwashima <kuniyu@google.com>,
Willem de Bruijn <willemb@google.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH 4/6 net-next] net: Convert proto_ops connect() callbacks to use sockaddr_unspec
Date: Thu, 24 Jul 2025 20:00:02 +0800 [thread overview]
Message-ID: <202507241955.kFMs4J5b-lkp@intel.com> (raw)
In-Reply-To: <20250723231921.2293685-4-kees@kernel.org>
Hi Kees,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20250723]
[cannot apply to net-next/main bluetooth-next/master bluetooth/master brauner-vfs/vfs.all mkl-can-next/testing mptcp/export mptcp/export-net trondmy-nfs/linux-next linus/master v6.16-rc7 v6.16-rc6 v6.16-rc5 v6.16-rc7]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Kees-Cook/net-uapi-Add-__kernel_sockaddr_unspec-for-sockaddr-of-unknown-length/20250724-072218
base: next-20250723
patch link: https://lore.kernel.org/r/20250723231921.2293685-4-kees%40kernel.org
patch subject: [PATCH 4/6 net-next] net: Convert proto_ops connect() callbacks to use sockaddr_unspec
config: x86_64-buildonly-randconfig-005-20250724 (https://download.01.org/0day-ci/archive/20250724/202507241955.kFMs4J5b-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250724/202507241955.kFMs4J5b-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202507241955.kFMs4J5b-lkp@intel.com/
All errors (new ones prefixed by >>):
>> net/mctp/af_mctp.c:632:13: error: incompatible function pointer types initializing 'int (*)(struct socket *, struct __kernel_sockaddr_unspec *, int, int)' with an expression of type 'int (struct socket *, struct sockaddr *, int, int)' [-Wincompatible-function-pointer-types]
632 | .connect = mctp_connect,
| ^~~~~~~~~~~~
1 error generated.
vim +632 net/mctp/af_mctp.c
63ed1aab3d40aa Matt Johnston 2022-02-09 627
8f601a1e4f8c84 Jeremy Kerr 2021-07-29 628 static const struct proto_ops mctp_dgram_ops = {
8f601a1e4f8c84 Jeremy Kerr 2021-07-29 629 .family = PF_MCTP,
8f601a1e4f8c84 Jeremy Kerr 2021-07-29 630 .release = mctp_release,
8f601a1e4f8c84 Jeremy Kerr 2021-07-29 631 .bind = mctp_bind,
3549eb08e55058 Matt Johnston 2025-07-10 @632 .connect = mctp_connect,
8f601a1e4f8c84 Jeremy Kerr 2021-07-29 633 .socketpair = sock_no_socketpair,
8f601a1e4f8c84 Jeremy Kerr 2021-07-29 634 .accept = sock_no_accept,
8f601a1e4f8c84 Jeremy Kerr 2021-07-29 635 .getname = sock_no_getname,
8f601a1e4f8c84 Jeremy Kerr 2021-07-29 636 .poll = datagram_poll,
63ed1aab3d40aa Matt Johnston 2022-02-09 637 .ioctl = mctp_ioctl,
8f601a1e4f8c84 Jeremy Kerr 2021-07-29 638 .gettstamp = sock_gettstamp,
8f601a1e4f8c84 Jeremy Kerr 2021-07-29 639 .listen = sock_no_listen,
8f601a1e4f8c84 Jeremy Kerr 2021-07-29 640 .shutdown = sock_no_shutdown,
8f601a1e4f8c84 Jeremy Kerr 2021-07-29 641 .setsockopt = mctp_setsockopt,
8f601a1e4f8c84 Jeremy Kerr 2021-07-29 642 .getsockopt = mctp_getsockopt,
8f601a1e4f8c84 Jeremy Kerr 2021-07-29 643 .sendmsg = mctp_sendmsg,
8f601a1e4f8c84 Jeremy Kerr 2021-07-29 644 .recvmsg = mctp_recvmsg,
8f601a1e4f8c84 Jeremy Kerr 2021-07-29 645 .mmap = sock_no_mmap,
63ed1aab3d40aa Matt Johnston 2022-02-09 646 #ifdef CONFIG_COMPAT
63ed1aab3d40aa Matt Johnston 2022-02-09 647 .compat_ioctl = mctp_compat_ioctl,
63ed1aab3d40aa Matt Johnston 2022-02-09 648 #endif
8f601a1e4f8c84 Jeremy Kerr 2021-07-29 649 };
8f601a1e4f8c84 Jeremy Kerr 2021-07-29 650
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-07-24 12:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 23:19 [PATCH 0/6 net-next] net: Introduce struct sockaddr_unspec Kees Cook
2025-07-23 23:19 ` [PATCH 1/6 net-next] net: uapi: Add __kernel_sockaddr_unspec for sockaddr of unknown length Kees Cook
2025-07-24 21:40 ` Jakub Kicinski
2025-07-24 22:28 ` Kees Cook
2025-07-23 23:19 ` [PATCH 2/6 net-next] net/l2tp: Add missing sa_family validation in pppol2tp_sockaddr_get_info Kees Cook
2025-07-23 23:19 ` [PATCH 3/6 net-next] net: Convert proto_ops bind() callbacks to use sockaddr_unspec Kees Cook
2025-07-24 11:29 ` kernel test robot
2025-07-24 13:31 ` Kees Cook
2025-07-24 13:02 ` kernel test robot
2025-07-23 23:19 ` [PATCH 4/6 net-next] net: Convert proto_ops connect() " Kees Cook
2025-07-24 12:00 ` kernel test robot [this message]
2025-07-23 23:19 ` [PATCH 5/6 net-next] net: Remove struct sockaddr from net.h Kees Cook
2025-07-23 23:19 ` [PATCH 6/6 net-next] net: Convert proto callbacks from sockaddr to sockaddr_unspec Kees Cook
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=202507241955.kFMs4J5b-lkp@intel.com \
--to=lkp@intel.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=llvm@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=willemb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.