From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hall.aurel32.net (hall.aurel32.net [IPv6:2001:bc8:30d7:100::1]) by sourceware.org (Postfix) with ESMTPS id 2600C385829F for ; Fri, 5 Aug 2022 21:44:47 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 2600C385829F Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=aurel32.net Authentication-Results: sourceware.org; spf=none smtp.mailfrom=aurel32.net DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=aurel32.net ; s=202004.hall; h=In-Reply-To:Content-Type:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Content-Transfer-Encoding:From:Reply-To: Subject:Content-ID:Content-Description:X-Debbugs-Cc; bh=qsZ3KALA1j82dk5zkHPYKczzqJR+DikICcfRlAPksH0=; b=bG7xqkS4pfA/5jkblLgARMCe52 XQ0HPBw9vdRWLK+BiUUox5M+jkDoYq6Tt4kSlZWPHXtH/ge0xybcMFsEPP+qR3uBvtNFNSyYRbo58 ZdDSYV6emj247PINhnwSx4wT2PK73JGmHjyZybZqjw3N6OWBdvNjfIYJpAoxt2eSyS7DJ6GSPMYQv xqFE0nAkgnyhtxmA3pfUbGE9Wv8jz4w2OIt9mibInqFhQfrc0JBZbv+/6rsjxObrHP+ZqlSKjLzaX rWg+ovvXiRnA2VPvRLuvzMFrmt21kp+3k++0zkpY5mOpm1K22NZNec2OvlzY+ACHk/0xrPmOdKTGk V+iWQ4VQ==; Received: from ohm.aurel32.net ([2001:bc8:30d7:111::1000]) by hall.aurel32.net with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1oK57b-001UJq-JU; Fri, 05 Aug 2022 23:44:43 +0200 Received: from aurel32 by ohm.aurel32.net with local (Exim 4.96) (envelope-from ) id 1oK57a-001ibO-1O; Fri, 05 Aug 2022 23:44:42 +0200 Date: Fri, 5 Aug 2022 23:44:42 +0200 From: Aurelien Jarno To: Palmer Dabbelt Cc: joseph@codesourcery.com, libc-alpha@sourceware.org Subject: Re: Update syscall lists for Linux 5.19 Message-ID: Mail-Followup-To: Palmer Dabbelt , joseph@codesourcery.com, libc-alpha@sourceware.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.2.6 (2022-06-05) X-Spam-Status: No, score=-13.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, GIT_PATCH_0, KAM_NUMSUBJECT, SPF_HELO_PASS, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Aug 2022 21:44:49 -0000 On 2022-08-05 10:28, Palmer Dabbelt wrote: > On Fri, 05 Aug 2022 07:42:48 PDT (-0700), aurelien@aurel32.net wrote: > > On 2022-08-03 17:36, Palmer Dabbelt wrote: > > > On Tue, 02 Aug 2022 12:23:42 PDT (-0700), joseph@codesourcery.com wrote: > > > > Linux 5.19 has no new syscalls, but enables memfd_secret in the uapi > > > > headers for RISC-V. Update the version number in syscall-names.list > > > > to reflect that it is still current for 5.19 and regenerate the > > > > arch-syscall.h headers with build-many-glibcs.py update-syscalls. > > > > > > > > Tested with build-many-glibcs.py. > > > > > > > > diff --git a/sysdeps/unix/sysv/linux/riscv/rv32/arch-syscall.h b/sysdeps/unix/sysv/linux/riscv/rv32/arch-syscall.h > > > > index bf4be80..202520e 100644 > > > > --- a/sysdeps/unix/sysv/linux/riscv/rv32/arch-syscall.h > > > > +++ b/sysdeps/unix/sysv/linux/riscv/rv32/arch-syscall.h > > > > @@ -122,6 +122,7 @@ > > > > #define __NR_mbind 235 > > > > #define __NR_membarrier 283 > > > > #define __NR_memfd_create 279 > > > > +#define __NR_memfd_secret 447 > > > > #define __NR_migrate_pages 238 > > > > #define __NR_mincore 232 > > > > #define __NR_mkdirat 34 > > > > diff --git a/sysdeps/unix/sysv/linux/riscv/rv64/arch-syscall.h b/sysdeps/unix/sysv/linux/riscv/rv64/arch-syscall.h > > > > index d656aed..4e65f33 100644 > > > > --- a/sysdeps/unix/sysv/linux/riscv/rv64/arch-syscall.h > > > > +++ b/sysdeps/unix/sysv/linux/riscv/rv64/arch-syscall.h > > > > @@ -127,6 +127,7 @@ > > > > #define __NR_mbind 235 > > > > #define __NR_membarrier 283 > > > > #define __NR_memfd_create 279 > > > > +#define __NR_memfd_secret 447 > > > > #define __NR_migrate_pages 238 > > > > #define __NR_mincore 232 > > > > #define __NR_mkdirat 34 > > > > diff --git a/sysdeps/unix/sysv/linux/syscall-names.list b/sysdeps/unix/sysv/linux/syscall-names.list > > > > index 6c7b2f7..028ad31 100644 > > > > --- a/sysdeps/unix/sysv/linux/syscall-names.list > > > > +++ b/sysdeps/unix/sysv/linux/syscall-names.list > > > > @@ -21,8 +21,8 @@ > > > > # This file can list all potential system calls. The names are only > > > > # used if the installed kernel headers also provide them. > > > > > > > > -# The list of system calls is current as of Linux 5.18. > > > > -kernel 5.18 > > > > +# The list of system calls is current as of Linux 5.19. > > > > +kernel 5.19 > > > > > > > > FAST_atomic_update > > > > FAST_cmpxchg > > > > > > Thanks, this was just a bug in the uapi headers: the syscall itself was has > > > been implemented since 7bb7f2ac24a0 ("arch, mm: wire up memfd_secret system > > > call where relevant"), which IIUC was first released in 5.14. The fix > > > should get backported. > > > > It got backported in 5.18.3. > > Sorry if that was the wrong thing to do, I thought this was safe because it > was just making the number availiable in the headers. > > > > I don't think any of that matters so much here, though. > > > > The backport causes the misc/tst-glibcsyscalls test to fail on the > > stable branches (tested on 2.35, but I guess it's the same on 2.36): > > > > | original exit status 1 > > | error: kernel syscall 'memfd_secret' (447) not known to glibc > > | info: glibc tables are based on kernel version 5.18 > > | info: installed kernel headers are version 5.18 > > > > So I wonder if we should just backport this commit to the stable > > branches to fix this failure. > > That works for me. Another option would be to revert the backport in Linux. > Either way we're stuck with some combination of releases that fail, so I'm > not sure which is better. No I do not think it is so bad. Errors are only reported when glibc headers version >= kernel version (otherwise they are just warnings). So if we increase glibc headers version to 5.18 by backporting this patch, they won't be errors anymore with kernel headers 5.18.y or older. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://www.aurel32.net