From: Al Viro <viro@zeniv.linux.org.uk>
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 04:09:29 +0000 [thread overview]
Message-ID: <20200105040929.GD8904@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAE90CG6SGWKXToVhY5VH-AzUjC6UEwRzoisUXM0OQe9XgcCHRA@mail.gmail.com>
On Sun, Jan 05, 2020 at 04:47:33AM +0100, Evan Rudford wrote:
> - Although the kernel will always remain in C, make serious efforts to
> introduce a safe language for kernel modules and perhaps for some
> subsystems.
Let me see if I've got it right - you suggest introducing an infrastructure
that would provide the bindings between the core kernel and those "safe
language modules" and maintaining its safety (from those languages' point
of view) through the changes of said core kernel *and* through the changes
of ABI of the languages in question? That takes an impressive skillset
from the poor sods in question - on the level of people actively working
on the language implementation, _in_ _addition_ _to_ what's normally
required for the kernel work. And that happy group would have to keep
track of the kernel changes. That will certainly make everything more
secure; I just wonder where have you found the funding to cover the costs
of psychiatric care for the victims^Wproud members of that august group.
You do have that funding lined up, right?
next prev parent reply other threads:[~2020-01-05 4:09 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 [this message]
2020-01-05 21:28 ` Theodore Y. 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=20200105040929.GD8904@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--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