From: Jeff Arnold <jbarnold@MIT.EDU>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: A system for rebootless kernel security updates
Date: Tue, 29 Apr 2008 02:55:06 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0804281907150.28653@vinegar-pot.mit.edu> (raw)
In-Reply-To: <4815A721.1040101@firstfloor.org>
> The only sane way to make such extensions a generically usable linux
> feature is to merge them to mainline.
> Really it's far better to just merge if you want it to make it out of
> the "toy" stage.
You're probably right.
I'm willing to undertake the project of bringing the code up to kernel
coding standards so that it can eventually be considered for mainline.
I'll plan on undertaking this project if I don't receive feedback that I
shouldn't do so.
If people have concerns about the high-level design of the system, it
would be useful for me to know that information sooner rather than later.
If there's anything that I can do to facilitate feedback at this stage,
please let me know.
Thanks for the advice.
Jeff Arnold
jbarnold@mit.edu
next prev parent reply other threads:[~2008-04-29 6:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 18:59 Jeff Arnold
2008-04-23 21:37 ` FD Cami
2008-04-24 13:42 ` Andi Kleen
2008-04-28 6:18 ` Jeff Arnold
2008-04-28 10:29 ` Andi Kleen
2008-04-29 6:55 ` Jeff Arnold [this message]
2008-04-29 12:57 ` Dan Noe
2008-04-29 22:43 ` Jeff Arnold
2008-05-01 11:38 ` Enrico Weigelt
2008-05-01 13:35 ` David Collier-Brown
2008-04-24 13:43 ` Christian Hesse
2008-04-24 18:13 ` Jeff Arnold
2008-04-24 19:16 ` Christian Hesse
2008-04-28 6:11 ` Jeff Arnold
2008-04-24 14:26 Tomasz Chmielewski
2008-04-24 14:42 ` Andi Kleen
2008-04-27 10:17 ` Pavel Machek
2008-04-27 17:00 ` Gilles Espinasse
2008-04-27 17:49 ` Willy Tarreau
2008-04-27 19:51 ` Oliver Pinter
2008-04-27 19:58 ` Jesper Juhl
2008-04-28 19:07 ` Bill Davidsen
2008-04-29 23:39 ` Jeff Arnold
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=alpine.DEB.1.10.0804281907150.28653@vinegar-pot.mit.edu \
--to=jbarnold@mit.edu \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®