From: Muli Ben-Yehuda <muli@il.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Yitzchak Eidus <ieidus@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: changing internal kernel system mechanism in runtime by a module patch
Date: Fri, 17 Nov 2006 09:06:12 +0200 [thread overview]
Message-ID: <20061117070612.GE3735@rhun.zurich.ibm.com> (raw)
In-Reply-To: <20061117065828.GA25155@infradead.org>
On Fri, Nov 17, 2006 at 06:58:29AM +0000, Christoph Hellwig wrote:
> This kind of stuff is just sick. Better let them play with their research
> OS for this kind of thing :)
sick, research, what's the difference? :-)
> In practice any non-trivial bug fix requires
> changes to global data structures so reloading a module doesn't make
> sense.
... unless you have a mechanism (which k42 does) to interpose between
data structures and the users of said structures, which you can use to
decide when to repace them.
> And for module-specific problems you should be able to hack around using
> kprobes if you really need (but then again for a mission critical system
> you should have proper active-active failover clustering anyway)
I'm not advocating we merge this - nor have I seen the implementation
for Linux yet - no need to preemptively scorch it from orbit :-)
Cheers,
Muli
prev parent reply other threads:[~2006-11-17 7:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 19:19 Yitzchak Eidus
2006-11-16 19:29 ` Adrian Bunk
2006-11-16 21:49 ` Jan Engelhardt
2006-11-16 21:12 ` Stephen Hemminger
2006-11-17 6:47 ` Muli Ben-Yehuda
2006-11-17 6:58 ` Christoph Hellwig
2006-11-17 7:06 ` Muli Ben-Yehuda [this message]
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=20061117070612.GE3735@rhun.zurich.ibm.com \
--to=muli@il.ibm.com \
--cc=hch@infradead.org \
--cc=ieidus@gmail.com \
--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®