From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Evan Rudford <zocker76@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is the Linux kernel underfunded? Lack of quality and security?
Date: Sun, 5 Jan 2020 16:28:31 -0500 [thread overview]
Message-ID: <20200105212831.GD4253@mit.edu> (raw)
In-Reply-To: <CAE90CG6SGWKXToVhY5VH-AzUjC6UEwRzoisUXM0OQe9XgcCHRA@mail.gmail.com>
On Sun, Jan 05, 2020 at 04:47:33AM +0100, Evan Rudford wrote:
> The problem of underfunding plagues many open source projects.
> I wonder whether the Linux kernel suffers from underfunding in
> comparison to its global reach.
> Although code reviews and technical discussions are working well, I
> argue that the testing infrastructure of the kernel is lacking.
> Severe bugs are discovered late, and they are discovered by developers
> that should not be exposed to that amount of breakage.
> Moreover, I feel that security issues do not receive enough resources.
It sounds like you are unaware of the Kernel Self Protection Project
(KSPP), which is focused on proactively improving the kernel's
security features, and the KernelCI project. There is quite a lot of
work happening already.
One of the challenges is that is an extremely large number of
different ways a kernel can be configured, and that a *very* large
number of the bugs tend to be hardware specific. Running CI on all
possible hardware that might run Linux is really not practical; but
there is a very large number of tests being run on both VM's and on
those hardware platforms that companies who are donating hardware to
KernelCI care about.
Keep in mind that there is *always* the opportunity to do more testing
and QA work. Companies which care about specific hardware and
software configurations are contributing resources (both money and
engineering headcount) to improve the quality for those specific
configurations. So there is *always* opportunities where more
resources can improve any product. This is true whether you are
talking about, say, a $15,000 Ford Fiesta or a $115,000 Porsche 911.
If you have access to resources that you would like to contribute, and
have some specific areas where you would like to see improvement, we
can certainly put you in touch with the various organizations, such as
the Linux Foundation, which are organizing efforts such as KernelCI.
There are also a number of engineers from a goodly number of companies
contributing to the Kernel Self Protection Project. If you are
interested in getting involved, please see:
https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project
Cheers,
- Ted
prev parent reply other threads:[~2020-01-05 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 3:47 Is the Linux kernel underfunded? Lack of quality and security? Evan Rudford
2020-01-05 4:09 ` Al Viro
2020-01-05 21:28 ` Theodore Y. 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=20200105212831.GD4253@mit.edu \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=zocker76@gmail.com \
/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