linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Arnd Bergmann <arnd@arndb.de>, kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	 linux-kernel@vger.kernel.org, linux-hexagon@vger.kernel.org,
	 sparclinux@vger.kernel.org, linux-sh@vger.kernel.org,
	Dinh Nguyen <dinguyen@kernel.org>,
	Simon Schuster <schuster.simon+binutils@siemens-energy.com>,
	Linux-Arch <linux-arch@vger.kernel.org>,
	Christian Brauner <brauner@kernel.org>
Subject: Re: kernel/fork.c:3088:2: warning: clone3() entry point is missing, please fix
Date: Mon, 30 Jun 2025 08:30:25 +0200	[thread overview]
Message-ID: <57101e901013a8e6ff44e10c93d1689490c714bf.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <2ef5bc91-f56d-4c76-b12e-2797999cba72@app.fastmail.com>

Hi Arnd,

On Mon, 2025-06-30 at 08:14 +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.
> 
> 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.

I have seen that warning about clone3() missing but I was not aware that it's
an urgent issue to address. Do you have any suggestion on how to implement
that syscall?

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2025-06-30  6:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <202506282120.6vRwodm3-lkp@intel.com>
2025-06-30  6:14 ` kernel/fork.c:3088:2: warning: clone3() entry point is missing, please fix Arnd Bergmann
2025-06-30  6:30   ` John Paul Adrian Glaubitz [this message]
2025-06-30 10:02     ` Arnd Bergmann
2025-06-30 10:45       ` John Paul Adrian Glaubitz
2025-06-30 12:07         ` Arnd Bergmann
2025-06-30 15:24           ` Andreas Larsson
2025-07-01  8:49           ` Christian Brauner
2025-06-30  6:31   ` Philip Li

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=57101e901013a8e6ff44e10c93d1689490c714bf.camel@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=arnd@arndb.de \
    --cc=brauner@kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=schuster.simon+binutils@siemens-energy.com \
    --cc=sparclinux@vger.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;
as well as URLs for NNTP newsgroup(s).