All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikanth Karthikesan <knikanth@suse.de>
To: balbir@linux.vnet.ibm.com
Cc: ananth@in.ibm.com, linux-kernel@vger.kernel.org,
	davem@davemloft.net, mhiramat@redhat.com, contact@ksplice.com,
	jbarnold@ksplice.com, tabbott@ksplice.com, wdaher@ksplice.com,
	andersk@ksplice.com
Subject: Re: [RFC] kreplace: Rebootless kernel updates
Date: Mon, 24 Nov 2008 16:37:43 +0530	[thread overview]
Message-ID: <200811241637.44185.knikanth@suse.de> (raw)
In-Reply-To: <4926DC1B.1020809@linux.vnet.ibm.com>

On Friday 21 November 2008 21:34:43 Balbir Singh wrote:
> Ananth N Mavinakayanahalli wrote:
> > On Fri, Nov 21, 2008 at 05:20:25PM +0530, Nikanth Karthikesan wrote:
>
> I had a patch for x86 a long time ago in 2005, but I never posted it :(
>

I just didn't wanted to say that after some time. ;)

>
> Yes and we need to be careful about licensing, tainting the kernel with
> such an implementation.
>

Agreed.

> > Kprobes themselves provide enough ammunition to users to shoot themselves
> > in the foot, but this is way more dangerous than that.
> > ...
>
> Undoubtedly, but a good warning is the best way to keep people warned about
> running such code :) It is a useful thing to have and to run, but running
> it would take more guts than anything else.

Thanks for the comments.

Thanks
Nikanth Karthikesan



  parent reply	other threads:[~2008-11-24 11:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21 11:50 [RFC] kreplace: Rebootless kernel updates Nikanth Karthikesan
2008-11-21 13:38 ` Ananth N Mavinakayanahalli
2008-11-21 16:04   ` Balbir Singh
2008-11-21 17:29     ` Chris Friesen
2008-11-24 11:07     ` Nikanth Karthikesan [this message]
2008-11-24 11:07   ` Nikanth Karthikesan
2008-11-21 14:39 ` Masami Hiramatsu
2008-11-24 11:07   ` Nikanth Karthikesan
2008-11-24 15:15     ` Masami Hiramatsu
2008-11-26  2:48       ` Nikanth K
2008-11-21 20:19 ` Anders Kaseorg
2008-11-22  3:46 ` Jeff Arnold
2008-11-23 19:39   ` Andi Kleen
2008-11-23 20:53     ` Jeff Arnold
2008-11-24 11:07   ` Nikanth Karthikesan

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=200811241637.44185.knikanth@suse.de \
    --to=knikanth@suse.de \
    --cc=ananth@in.ibm.com \
    --cc=andersk@ksplice.com \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=contact@ksplice.com \
    --cc=davem@davemloft.net \
    --cc=jbarnold@ksplice.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@redhat.com \
    --cc=tabbott@ksplice.com \
    --cc=wdaher@ksplice.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.