From: "Theodore Ts'o" <tytso@mit.edu>
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 10:44:34 -0400 [thread overview]
Message-ID: <20240820144434.GA184464@mit.edu> (raw)
In-Reply-To: <D19DB99F-B5D9-49A6-BCF8-A5980A9BC1A0@gmail.com>
On Tue, Aug 20, 2024 at 09:49:59PM +0800, Miao Wang wrote:
>
> I agree with you and Cyril on the version numbers, recalling that kernels
> on RHEL numbered on 3.10 contains various new features.
Some enterprise kernel versions have also been known to completely
take code whole from some subsystem (like, for example, a file system
like ext4 or xfs) from much newer upstream kernel version and backport
it into a very old "enterprise" kernel, with massive work to deal with
the dependencies that might be needed by the newer code, and
additional massive work so that structures and function signatures
stay the same so that binary out-of-tree kernel modules can continue
to load on that "stable" enterprise kernel.
That might take huge amounts of effort from a quality assurance
perspective, but that's might some enterprise customers are willing to
pay $$$$ for that frankenkernel and support for that frankenkernel....
This is also why when I get a bug report relating a distro kernel, I
tell bug reporters to go back to the distro for support. Basically,
you can't really take anything for granted when you're dealing with a
non-upstream kernel, and that includes the version number.
Personally, I think this is a really bad idea, but distros and their
customers have the freedom to do what they want. And this is why
those customers pay the distro the big bucks. :-)
- Ted
prev parent reply other threads:[~2024-08-20 14:45 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
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 [this message]
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=20240820144434.GA184464@mit.edu \
--to=tytso@mit.edu \
--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;
as well as URLs for NNTP newsgroup(s).