From: Willy Tarreau <w@1wt.eu>
To: Zhangjin Wu <falcon@tinylab.org>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, thomas@t-8ch.de
Subject: Re: [PATCH v3 01/11] tools/nolibc: remove the old sys_stat support
Date: Sat, 15 Jul 2023 10:59:42 +0200 [thread overview]
Message-ID: <20230715085942.GB24086@1wt.eu> (raw)
In-Reply-To: <5319451b7e01f1d101b94dcecf195c734eb74ebc.1689150149.git.falcon@tinylab.org>
Hi Zhangjin,
On Wed, Jul 12, 2023 at 05:16:34PM +0800, Zhangjin Wu wrote:
> __NR_statx has been added from v4.10:
>
> commit a528d35e8bfc ("statx: Add a system call to make enhanced file info available")
>
> It has been supported by all of the platforms since at least from v4.20
> and glibc 2.28.
>
> Let's remove the old arch related and dependent sys_stat support
> completely.
>
> This is friendly to the future new architecture porting.
As I previously said, I'd like that we at least preserve compatibility
with supported stable branches. 4.14 and 4.19 are still supported, so
does this mean that if I rebuild my preinit against the updated nolibc
it will fail to boot on such older systems for the archs that we support?
Because if it means that in order to support all currently active
kernels, one must only build from an older copy of the lib, that becomes
a disservice to its development and usage. Thus if you checked that aarch64,
arm, i386, mips, riscv, s390 and x86_64 had already adopted statx by 4.14,
then I'm fine and we can drop stat(), but then it must be mentioned in
the commit message, because here it's not explicit.
Thanks!
Willy
next prev parent reply other threads:[~2023-07-15 9:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 9:15 [PATCH v3 00/11] tools/nolibc: shrink arch support Zhangjin Wu
2023-07-12 9:16 ` [PATCH v3 01/11] tools/nolibc: remove the old sys_stat support Zhangjin Wu
2023-07-15 8:59 ` Willy Tarreau [this message]
2023-07-15 10:39 ` Zhangjin Wu
2023-07-15 11:45 ` Willy Tarreau
2023-07-12 9:17 ` [PATCH v3 02/11] tools/nolibc: add new crt.h with _start_c Zhangjin Wu
2023-07-12 20:39 ` Thomas Weißschuh
2023-07-13 6:12 ` Zhangjin Wu
2023-07-13 6:23 ` Zhangjin Wu
2023-07-13 6:24 ` Thomas Weißschuh
2023-07-13 6:34 ` Willy Tarreau
2023-07-14 5:58 ` Zhangjin Wu
2023-07-14 6:34 ` Thomas Weißschuh
2023-07-14 9:47 ` Zhangjin Wu
2023-07-15 7:24 ` Thomas Weißschuh
2023-07-15 9:23 ` Zhangjin Wu
2023-07-15 9:57 ` Willy Tarreau
2023-07-12 9:18 ` [PATCH v3 03/11] tools/nolibc: arm: shrink _start " Zhangjin Wu
2023-07-12 9:19 ` [PATCH v3 04/11] tools/nolibc: aarch64: " Zhangjin Wu
2023-07-12 9:20 ` [PATCH v3 05/11] tools/nolibc: i386: " Zhangjin Wu
2023-07-12 9:22 ` [PATCH v3 06/11] tools/nolibc: x86_64: " Zhangjin Wu
2023-07-12 9:23 ` [PATCH v3 07/11] tools/nolibc: mips: " Zhangjin Wu
2023-07-12 9:24 ` [PATCH v3 08/11] tools/nolibc: loongarch: " Zhangjin Wu
2023-07-12 9:25 ` [PATCH v3 09/11] tools/nolibc: riscv: " Zhangjin Wu
2023-07-12 9:26 ` [PATCH v3 10/11] tools/nolibc: s390: " Zhangjin Wu
2023-07-12 9:27 ` [PATCH v3 11/11] tools/nolibc: arch-*.h: add missing space after ',' Zhangjin Wu
2023-07-15 10:01 ` [PATCH v3 00/11] tools/nolibc: shrink arch support Willy Tarreau
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=20230715085942.GB24086@1wt.eu \
--to=w@1wt.eu \
--cc=arnd@arndb.de \
--cc=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=thomas@t-8ch.de \
/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