Re: A system for rebootless kernel security updates

[Jeff Arnold <jbarnold@MIT.EDU>]

> You should consider bringing the kernel module up to kernel coding 
> standards and submitting it for mainline. That would be the best way to 
> get more users and testers.

I'm certainly interested in bringing the code up to kernel coding 
standards (for example, I'd be happy to address any issues with the code 
that are brought to my attention).  I'm not sure whether submitting it for 
mainline makes sense since the software doesn't significantly benefit from 
being bundled with the kernel.

Instead, it might be more important to 1) package the userspace 
update-construction software for common Linux distributions to make it 
easily available to interested users, and 2) to provide binary kernel 
updates for common distribution kernels so that users can simply sign up 
and get fewer "your machine needs to be rebooted now for an update to take 
effect" notifications.

I'm open to suggestions about how I should proceed, however.

> Have you also considered to turn it into a generic incremental binary
> linker too?

I've considered modifying the system for use in other contexts, but I 
don't think that I'll get around to such a project anytime soon; my 
current focus is on making it easier for people to perform rebootless 
kernel security updates.

Jeff Arnold
jbarnold@mit.edu