mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Laurijssen <lauserve@gmail.com>,
	linux-kernel@vger.kernel.org, pjw@kernel.org,
	akpm@linux-foundation.org, jannh@google.com, brauner@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Laurijssen <laurijssen@protonmail.com>
Subject: Re: [PATCH] add utsname_set_field to reuse code in setdomainname and sethostname
Date: Fri, 6 Nov 2026 23:56:05 +0800	[thread overview]
Message-ID: <202611062313.QD6BbpXI-lkp@intel.com> (raw)
In-Reply-To: <20261105120751.920311-1-laurijssen@protonmail.com>

Hi Laurijssen,

kernel test robot noticed the following build errors:

[auto build test ERROR on akpm-mm/mm-everything]
[also build test ERROR on brauner-vfs/vfs.all linus/master v7.4-rc1 next-20261105]
[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/Laurijssen/add-utsname_set_field-to-reuse-code-in-setdomainname-and-sethostname/20261105-130751
base:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link:    https://lore.kernel.org/r/20261105120751.920311-1-laurijssen%40protonmail.com
patch subject: [PATCH] add utsname_set_field to reuse code in setdomainname and sethostname
config: sh-randconfig-1000-20261106 (https://download.01.org/0day-ci/archive/20261106/202611062313.QD6BbpXI-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261106/202611062313.QD6BbpXI-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/202611062313.QD6BbpXI-lkp@intel.com/

All errors (new ones prefixed by >>):

   sh4-linux-ld: kernel/sys.o: in function `__se_sys_sethostname':
>> kernel/sys.c:1422:(.text+0x3d5c): undefined reference to `utsname_set_field'
   sh4-linux-ld: kernel/sys.o: in function `__se_sys_setdomainname':
   kernel/sys.c:1455:(.text+0x3edc): undefined reference to `utsname_set_field'


vim +1422 kernel/sys.c

5cacdb4add1b1e5 Christoph Hellwig 2010-03-10  1421  
5a8a82b1d306a32 Heiko Carstens    2009-01-14 @1422  SYSCALL_DEFINE2(sethostname, char __user *, name, int, len)
^1da177e4c3f415 Linus Torvalds    2005-04-16  1423  {
58c79d6f0053050 Laurijssen        2026-11-05  1424  	return utsname_set_field(name, len, UTS_PROC_HOSTNAME);
^1da177e4c3f415 Linus Torvalds    2005-04-16  1425  }
^1da177e4c3f415 Linus Torvalds    2005-04-16  1426  

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2026-11-06 15:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05 12:07 Laurijssen
2026-11-06 15:56 ` kernel test robot [this message]
2026-11-06 16:31 ` kernel test robot

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=202611062313.QD6BbpXI-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=jannh@google.com \
    --cc=laurijssen@protonmail.com \
    --cc=lauserve@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pjw@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®