From: Andrew Morton <akpm@linux-foundation.org>
To: Tim Abbott <tabbott@ksplice.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Jon Masters <jonathan@jonmasters.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Arjan van de Ven <arjan@infradead.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
Anders Kaseorg <andersk@ksplice.com>,
Jeffrey B Arnold <jbarnold@ksplice.com>,
"Waseem S. Daher" <wdaher@ksplice.com>
Subject: Re: [PATCH] Add new TAINT_KSPLICE flag for when a Ksplice update has been loaded.
Date: Mon, 22 Jun 2009 07:53:46 -0700 [thread overview]
Message-ID: <20090622075346.e9489feb.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0906220928010.26465@vinegar-pot.mit.edu>
On Mon, 22 Jun 2009 09:32:13 -0400 (EDT) Tim Abbott <tabbott@ksplice.com> wrote:
> On Mon, 22 Jun 2009, Peter Zijlstra wrote:
>
> > But without ksplice patches you cannot ksplice, right? That is, there is
> > a non trivial patch to the kernel to make this happen afaik. If distros
> > ship that, then they can add this taint flag as well. No need to burden
> > mainline with any of that until it ksplice proper makes it in.
>
> No, Ksplice can patch completely unmodified upstream and distribution
> kernels.
>
Have the ksplice people considered using /proc/sys/kernel/tainted and
TAINT_USER?
next prev parent reply other threads:[~2009-06-22 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 19:57 [PATCH] Add new TAINT_KSPLICE flag for when a Ksplice update has been loaded Tim Abbott
2009-06-19 20:11 ` Peter Zijlstra
2009-06-22 7:51 ` Jon Masters
2009-06-22 8:50 ` Peter Zijlstra
2009-06-22 13:32 ` Tim Abbott
2009-06-22 14:53 ` Andrew Morton [this message]
2009-06-23 18:56 ` Tim Abbott
2009-06-22 21:25 ` Jon Masters
2009-06-22 17:46 ` Chuck Ebbert
2009-06-22 19:59 ` Maxim Levitsky
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=20090622075346.e9489feb.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=andersk@ksplice.com \
--cc=arjan@infradead.org \
--cc=jbarnold@ksplice.com \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tabbott@ksplice.com \
--cc=torvalds@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox