linux-kernel - Re: kernel/fork.c:3088:2: warning: clone3() entry point is missing, please fix

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aGIvWBeEQuy7QgfK@rli9-mobl>
Date: Mon, 30 Jun 2025 14:31:52 +0800
From: Philip Li <philip.li@...el.com>
To: Arnd Bergmann <arnd@...db.de>
CC: kernel test robot <lkp@...el.com>, <llvm@...ts.linux.dev>,
	<oe-kbuild-all@...ts.linux.dev>, <linux-kernel@...r.kernel.org>,
	<linux-hexagon@...r.kernel.org>, <sparclinux@...r.kernel.org>,
	<linux-sh@...r.kernel.org>, Dinh Nguyen <dinguyen@...nel.org>, Simon Schuster
	<schuster.simon+binutils@...mens-energy.com>, Linux-Arch
	<linux-arch@...r.kernel.org>, Christian Brauner <brauner@...nel.org>
Subject: Re: kernel/fork.c:3088:2: warning: clone3() entry point is missing,
 please fix

On Mon, Jun 30, 2025 at 08:14:16AM +0200, Arnd Bergmann wrote:
> On Sat, Jun 28, 2025, at 21:59, kernel test robot wrote:
> > Hi Arnd,
> >
> > FYI, the error/warning still remains.
> >
> > date:   12 months ago
> > config: hexagon-randconfig-2002-20250626 
> > (https://download.01.org/0day-ci/archive/20250628/202506282120.6vRwodm3-lkp@intel.com/config)
> > commit: 505d66d1abfb90853e24ab6cbdf83b611473d6fc clone3: drop __ARCH_WANT_SYS_CLONE3 macro
> >> kernel/fork.c:3088:2: warning: clone3() entry point is missing, please fix [-W#warnings]
> 
> My patch only moved the warning about the four broken architectures
> (hexagon, sparc, sh, nios2) that have never implemented the clone3
> syscall from commit 7f192e3cd316 ("fork: add clone3"), over six years
> ago.

Sorry for the false positive, I will configure the bot to avoid sending
this again.

> 
> I usually try to fix warnings when I get them, but the entire point
> why these still exist is that they require someone to add the
> syscall with the correct calling conventions for the respective
> architecture and make sure this actually works correctly.
> 
> I don't think any of those architecture maintainers are paying
> attention to the build warnings or the lkp reports, and they are
> clearly not trying to fix them any more, so maybe it's better to
> just stop testing them in lkp.

Thanks for the comments, we will consider to adjust the priority for
the related archs. Also welcome more inputs for how to test and report
out issues of these archs.

> 
>     Arnd
>