On Wed, 14 Jan 2026 at 00:13, kernel test robot <[email protected]> wrote: > > Hi Bobby, > > kernel test robot noticed the following build warnings: > > [auto build test WARNING on net-next/main] > > url: > https://github.com/intel-lab-lkp/linux/commits/Bobby-Eshleman/virtio-set-skb-owner-of-virtio_transport_reset_no_sock-reply/20260113-125559 > base: net-next/main > patch link: > https://lore.kernel.org/r/20260112-vsock-vmtest-v14-1-a5c332db3e2b%40meta.com > patch subject: [PATCH net-next v14 01/12] vsock: add netns to vsock core > config: x86_64-buildonly-randconfig-004-20260113 > (https://download.01.org/0day-ci/archive/20260114/[email protected]/config) > compiler: gcc-14 (Debian 14.2.0-19) 14.2.0 > reproduce (this is a W=1 build): > (https://download.01.org/0day-ci/archive/20260114/[email protected]/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 <[email protected]> > | Closes: > https://lore.kernel.org/oe-kbuild-all/[email protected]/ > > All warnings (new ones prefixed by >>, old ones prefixed by <<): > > >> WARNING: modpost: net/vmw_vsock/vsock: section mismatch in reference: > >> vsock_exit+0x25 (section: .exit.text) -> vsock_sysctl_ops (section: > >> .init.data)
Bobby can you check this report? Could be related to `__net_initdata` annotation of `vsock_sysctl_ops` ? Why we need that? Thanks, Stefano
