Page 1 of 2 12 LastLast
Results 1 to 10 of 20

Thread: Red Hat Intros Kpatch For Dynamic Kernel Patching

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    14,904

    Default Red Hat Intros Kpatch For Dynamic Kernel Patching

    Phoronix: Red Hat Intros Kpatch For Dynamic Kernel Patching

    Red Hat's latest open-source contribution to the Linux community is Kpatch, yet another means of dynamic patching for the Linux kernel...

    http://www.phoronix.com/vr.php?view=MTYyMTE

  2. #2
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    5,128

    Default

    inb4 both RH and Suse solutions get upstream, and a rootkit uses each to patch the other out at runtime.

  3. #3
    Join Date
    Jul 2012
    Posts
    771

    Default

    Why do we need 3 of them?

  4. #4
    Join Date
    Jun 2009
    Posts
    558

    Default

    Ksplice, Kgraft and now Kpatch.

    NIH syndrome at its best. And i'll bet that Kpatch eventually gets upstreamed just because it's from Red Hat.

  5. #5
    Join Date
    Nov 2010
    Posts
    73

    Default

    Quote Originally Posted by Sonadow View Post
    Ksplice, Kgraft and now Kpatch.

    NIH syndrome at its best. And i'll bet that Kpatch eventually gets upstreamed just because it's from Red Hat.
    if kpatch gets upstreamed that's because it's the best solution. not just because it was developed by redhat - that's how it works.

    I would not be surprised if the code that will be merged upstream would not contain parts from both kgraft an kpatch.

  6. #6
    Join Date
    Jun 2006
    Location
    Portugal
    Posts
    530

    Default

    Quote Originally Posted by Sonadow View Post
    Ksplice, Kgraft and now Kpatch.

    NIH syndrome at its best. And i'll bet that Kpatch eventually gets upstreamed just because it's from Red Hat.
    Yes because linux kernel development has never duplicated effort until the developers reach a consensus and one is chosen.
    We must observe this phenomena closely!

  7. #7
    Join Date
    Jul 2013
    Posts
    7

    Default

    I never really understood why anyone would want to do this. I would think, even on systems that need to maximize up time, you would want to do scheduled maintenance once in a while. This way you know exactly how the system will behave on shutdown/startup so when unintended downtime occurs you aren't blindsided by something odd.

  8. #8

    Default

    Quote Originally Posted by Sonadow View Post
    Ksplice, Kgraft and now Kpatch.

    NIH syndrome at its best. And i'll bet that Kpatch eventually gets upstreamed just because it's from Red Hat.
    kGraft was publicly announced on 2014-01-31: https://www.suse.com/communities/con...rnel-patching/

    The announcement for Kpatch states that "the kernel team here at Red Hat has been working on a dynamic kernel patching project called kpatch for several months."

    So, sounds like it was just a timing thing: both teams happened to work on the same thing at the same time. I don't know anything the public doesn't about Kpatch, but RH and SUSE devs have a long history of working together upstream, esp. on the kernel, so I'd be surprised if that doesn't happen here.

    edit: looks like http://www.pro-linux.de/news/1/20758...it-kpatch.html may be vaguely interesting - anyone who can read German want to translate?

  9. #9
    Join Date
    Oct 2012
    Location
    Sweden
    Posts
    313

    Default

    I'd prefer if KGraft came out ahead, just to give a few points to SUSE. Red Hat have enough.

  10. #10
    Join Date
    Mar 2014
    Posts
    1

    Default

    Quote Originally Posted by AdamW View Post
    kGraft was publicly announced on 2014-01-31: https://www.suse.com/communities/con...rnel-patching/

    The announcement for Kpatch states that "the kernel team here at Red Hat has been working on a dynamic kernel patching project called kpatch for several months."

    So, sounds like it was just a timing thing: both teams happened to work on the same thing at the same time. I don't know anything the public doesn't about Kpatch, but RH and SUSE devs have a long history of working together upstream, esp. on the kernel, so I'd be surprised if that doesn't happen here.

    edit: looks like http://www.pro-linux.de/news/1/20758...it-kpatch.html may be vaguely interesting - anyone who can read German want to translate?
    I'll give it a try:

    Red Hat's Kpatch joins Kspilce and Kgraft

    A week after Suse announced that they work on Kgraft, a framework for live patching of the kernel, Red Hat explained that they want to present their own software, named Kpatch at the end of march at the Collaboration Summit. This was unveilled by a Red Hat developer named Linda Wang in a lightning talk at devconf.cz.

    Beneath Ksplice and OpenSuses Kgraft, this is the third technology in development for patching at the kernel runtime and without reboots. Ksplice has been in development since 2008, but was bought by Oracle in 2011 and hasn't been available under a free license since. Aditionally Ksplice wasn't upstreamed.

    Suse and Red Hat still seem to be in early developement with those technologies, but it's unclear why both distributions are working on similar things at the same time instead of sharing the work. Concerning integration into mainline, it seems unlikely that two interfaces will be accepted.

    The last paragraph is about why such a technology is needed anyways and not about the differences or anything like that, plus it links to a english website.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •