From: Willy Tarreau <w@1wt.eu>
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 20:30:29 +0200 [thread overview]
Message-ID: <ZsTgxUndhb04snd6@1wt.eu> (raw)
In-Reply-To: <46C6EB05-1AA2-42BF-82BF-3B99CCA57439@gmail.com>
On Wed, Aug 21, 2024 at 12:09:41AM +0800, Miao Wang wrote:
> However, my original question is whether it is expected to include new
> syscalls in kernel stable tree. According to the document "stable-kernel-
> rules", if I'm interpreting it correctly, I expect only bug fixes and small
> driver enhancements from stable releases. I understand the patch in question
> is actually introducing new syscalls, which is beyond my expectation. So I
> wonder the consideration of including this patch in stable releases.
When you maintain stable software you quickly realize that everything
is not just pure white or black but a shade of gray and that if it can
be considered as a bug to miss a syscall in certain environments for
example, then it can become a valid fix to add it. I don't have any
opinion on this particular one, but since your question is broader I'm
trying to explain.
Different people have different expectations about what needs to be
fixed, that's even why some people will choose a distro over another
one (prefer to fix only critical bugs over fixing all bugs for example),
but there's no point restarting a philosophical on this topic which has
already been rehashed too many times in the past.
As a rule of thumb, just keep in mind that anything that needs to get
fix will eventually be fixed.
Thanks,
Willy
next prev parent reply other threads:[~2024-08-20 18: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
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 [this message]
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=ZsTgxUndhb04snd6@1wt.eu \
--to=w@1wt.eu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.