ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] live patching
Date: Fri, 16 Oct 2015 21:34:13 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1510162130430.21100@pobox.suse.cz> (raw)
In-Reply-To: <alpine.LNX.2.00.1510131125570.21100@pobox.suse.cz>

On Tue, 13 Oct 2015, Jiri Kosina wrote:

> quite frankly, I think the need for discussing this has temporarily 
> diminished, because currently common preparatory steps are being worked on 
> (which are generally beneficial even without live patching) -- namely 
> Josh's work on reliable stack traces.

Oh, and also rather important aspect -- the relevance of this topic quite 
depends on the folks that will be present (is the invitee list available 
somewhere by any chance?).

To sum this one up -- I can definitely give a short summary of the status 
quo of the live patching efforts (both what's currently merged and what's 
currently being worked on), but I am not sure how much interesting that's 
for general KS folk. The more controversial discussions are temporarily 
paused for the time being; I expect them to be resume within a few months 
from now.

Thanks,

-- 
Jiri Kosina
SUSE Labs

      reply	other threads:[~2015-10-16 19:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07 20:42 Jiri Kosina
2015-07-08 16:13 ` Masami Hiramatsu
2015-07-08 21:21   ` Jiri Kosina
2015-07-09  3:26   ` Kamezawa Hiroyuki
2015-07-09  9:56     ` Jiri Kosina
2015-07-09 10:05       ` Kamezawa Hiroyuki
2015-10-12 17:13 ` Theodore Ts'o
2015-10-13  9:29   ` Jiri Kosina
2015-10-16 19:34     ` Jiri Kosina [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=alpine.LNX.2.00.1510162130430.21100@pobox.suse.cz \
    --to=jikos@kernel.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=tytso@mit.edu \
    /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