From: kernel test robot <lkp@intel.com>
To: Pengpeng Hou <pengpeng@iscas.ac.cn>,
richard@nod.at, anton.ivanov@cambridgegreys.com,
johannes@sipsolutions.net
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-um@lists.infradead.org, linux-kernel@vger.kernel.org,
pengpeng@iscas.ac.cn
Subject: Re: [PATCH] um: mconsole: validate notify socket path length
Date: Tue, 31 Mar 2026 23:38:56 +0800 [thread overview]
Message-ID: <202603312307.FOQx0THR-lkp@intel.com> (raw)
In-Reply-To: <20260329030945.32368-1-pengpeng@iscas.ac.cn>
Hi Pengpeng,
kernel test robot noticed the following build errors:
[auto build test ERROR on uml/next]
[also build test ERROR on wireless-next/main wireless/main uml/fixes linus/master v7.0-rc6 next-20260330]
[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/Pengpeng-Hou/um-mconsole-validate-notify-socket-path-length/20260331-052930
base: https://git.kernel.org/pub/scm/linux/kernel/git/uml/linux next
patch link: https://lore.kernel.org/r/20260329030945.32368-1-pengpeng%40iscas.ac.cn
patch subject: [PATCH] um: mconsole: validate notify socket path length
config: um-defconfig (https://download.01.org/0day-ci/archive/20260331/202603312307.FOQx0THR-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 2cd67b8b69f78e3f95918204320c3075a74ba16c)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260331/202603312307.FOQx0THR-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/202603312307.FOQx0THR-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/um/drivers/mconsole_user.c:203:6: error: call to undeclared function 'snprintf'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
203 | if (snprintf(target.sun_path, sizeof(target.sun_path), "%s", sock_name) >=
| ^
1 error generated.
vim +/snprintf +203 arch/um/drivers/mconsole_user.c
180
181 int mconsole_notify(char *sock_name, int type, const void *data, int len)
182 {
183 struct sockaddr_un target;
184 struct mconsole_notify packet;
185 int n, err = 0;
186
187 lock_notify();
188 if (notify_sock < 0) {
189 notify_sock = socket(PF_UNIX, SOCK_DGRAM, 0);
190 if (notify_sock < 0) {
191 err = -errno;
192 printk(UM_KERN_ERR "mconsole_notify - socket failed, "
193 "errno = %d\n", errno);
194 }
195 }
196 unlock_notify();
197
198 if (err)
199 return err;
200
201 memset(&target, 0, sizeof(target));
202 target.sun_family = AF_UNIX;
> 203 if (snprintf(target.sun_path, sizeof(target.sun_path), "%s", sock_name) >=
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-03-31 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 3:09 [PATCH] um: mconsole: validate notify socket path length Pengpeng Hou
2026-03-31 15:16 ` kernel test robot
2026-03-31 15:38 ` kernel test robot [this message]
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=202603312307.FOQx0THR-lkp@intel.com \
--to=lkp@intel.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pengpeng@iscas.ac.cn \
--cc=richard@nod.at \
/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.