From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android14-6.1-2025-04 2/2] net/core/scm.c:95:24: error: no member named 'vertices' in 'struct scm_fp_list'
Date: Tue, 31 Mar 2026 17:11:16 +0800 [thread overview]
Message-ID: <202603311752.sZffzSwV-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android14-6.1-2025-04
head: a01f4f3e3d4d93656a40a6739b171e98bd608766
commit: 9b0889c42a173c7b6a1891893f3d619166d37efa [2/2] UPSTREAM: af_unix: Allocate struct unix_vertex for each inflight AF_UNIX fd.
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20260331/202603311752.sZffzSwV-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260331/202603311752.sZffzSwV-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/202603311752.sZffzSwV-lkp@intel.com/
All errors (new ones prefixed by >>):
>> net/core/scm.c:95:24: error: no member named 'vertices' in 'struct scm_fp_list'
95 | INIT_LIST_HEAD(&fpl->vertices);
| ~~~ ^
net/core/scm.c:384:28: error: no member named 'vertices' in 'struct scm_fp_list'
384 | INIT_LIST_HEAD(&new_fpl->vertices);
| ~~~~~~~ ^
2 errors generated.
vim +95 net/core/scm.c
68
69 static int scm_fp_copy(struct cmsghdr *cmsg, struct scm_fp_list **fplp)
70 {
71 int *fdp = (int*)CMSG_DATA(cmsg);
72 struct scm_fp_list *fpl = *fplp;
73 struct file **fpp;
74 int i, num;
75
76 num = (cmsg->cmsg_len - sizeof(struct cmsghdr))/sizeof(int);
77
78 if (num <= 0)
79 return 0;
80
81 if (num > SCM_MAX_FD)
82 return -EINVAL;
83
84 if (!fpl)
85 {
86 fpl = kmalloc(sizeof(struct scm_fp_list), GFP_KERNEL_ACCOUNT);
87 if (!fpl)
88 return -ENOMEM;
89 *fplp = fpl;
90 fpl->count = 0;
91 fpl->count_unix = 0;
92 fpl->max = SCM_MAX_FD;
93 fpl->user = NULL;
94 #if IS_ENABLED(CONFIG_UNIX)
> 95 INIT_LIST_HEAD(&fpl->vertices);
96 #endif
97 }
98 fpp = &fpl->fp[fpl->count];
99
100 if (fpl->count + num > fpl->max)
101 return -EINVAL;
102
103 /*
104 * Verify the descriptors and increment the usage count.
105 */
106
107 for (i=0; i< num; i++)
108 {
109 int fd = fdp[i];
110 struct file *file;
111
112 if (fd < 0 || !(file = fget_raw(fd)))
113 return -EBADF;
114 /* don't allow io_uring files */
115 if (io_is_uring_fops(file)) {
116 fput(file);
117 return -EINVAL;
118 }
119 if (unix_get_socket(file))
120 fpl->count_unix++;
121
122 *fpp++ = file;
123 fpl->count++;
124 }
125
126 if (!fpl->user)
127 fpl->user = get_uid(current_user());
128
129 return num;
130 }
131
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-31 9:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202603311752.sZffzSwV-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.