From: Cyril Hrubis <chrubis@suse.cz>
To: Miao Wang <shankerwangmiao@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Xi Ruoyao <xry111@xry111.site>,
Huacai Chen <chenhuacai@kernel.org>,
loongarch@lists.linux.dev, Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, WANG Xuerui <kernel@xen0n.name>,
linux-api@vger.kernel.org
Subject: Re: It is correct to introduce new sys calls to stable versions?
Date: Tue, 20 Aug 2024 15:29:08 +0200 [thread overview]
Message-ID: <ZsSaJKKyLuH_vZ1C@yuki.lan> (raw)
In-Reply-To: <DF762B6F-360A-4C0C-8C85-55686417209B@gmail.com>
Hi!
> I wonder if it is correct to add new syscalls, which actually changes
> the kernel features, in stable releases, as it might confuse downstream
> developers because they may assume the existence of a certain feature
> after a certain version.
Just a side note, one thing I've learned by maintaining the Linux Test
Project is that the kernel version is a lie. You should not use the
kernel version for anything, never. All distributions rutinely backport
various new functionalities to older kernels and only reliable way how
to make sure something is implemented is to call the syscall and check
the return value.
That being said I have no idea what rules apply to stable trees.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2024-08-20 13:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 13:19 It is correct to introduce new sys calls to stable versions? Miao Wang
2024-08-20 13:29 ` Cyril Hrubis [this message]
2024-08-20 13:36 ` Greg Kroah-Hartman
2024-08-20 13:49 ` Miao Wang
2024-08-20 14:00 ` Greg Kroah-Hartman
2024-08-20 15:05 ` Willy Tarreau
2024-08-20 16:09 ` Miao Wang
2024-08-20 18:30 ` Willy Tarreau
2024-08-20 19:24 ` Miao Wang
2024-08-20 14:44 ` Theodore Ts'o
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=ZsSaJKKyLuH_vZ1C@yuki.lan \
--to=chrubis@suse.cz \
--cc=chenhuacai@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@xen0n.name \
--cc=linux-api@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=shankerwangmiao@gmail.com \
--cc=stable@vger.kernel.org \
--cc=xry111@xry111.site \
/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