From: George Dunlap <george.dunlap@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
konrad@kernel.org, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Ross Lagerwall <ross.lagerwall@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 1/3] livepach: Add .livepatch.hooks functions and test-case
Date: Mon, 8 Aug 2016 14:42:45 +0100 [thread overview]
Message-ID: <819874b1-ccdf-9d82-844e-401f63a8daff@citrix.com> (raw)
In-Reply-To: <57A4CE7502000078001034E6@prv-mh.provo.novell.com>
On 05/08/16 16:35, Jan Beulich wrote:
>>>> On 04.08.16 at 17:49, <konrad.wilk@oracle.com> wrote:
>> In general, the hooks provide flexibility when having to deal with
>> unforeseen cases, but their application should be rarely required (<
>> 10%)."
>
> But the greater flexibility of course comes with increased chances
> of screwing things up. I'm therefore still not entirely convinced that
> such XSAs wouldn't then better not be live patched.
But this functionality is optional, right? So although I tend to agree
with you, we can let the person / organization preparing the patch take
that risk if they want to?
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-08-08 13:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 15:49 [PATCH v1] Livepatch patches for v4.8 (v1) Konrad Rzeszutek Wilk
2016-08-04 15:49 ` [PATCH v2 1/3] livepach: Add .livepatch.hooks functions and test-case Konrad Rzeszutek Wilk
2016-08-05 15:35 ` Jan Beulich
2016-08-05 21:08 ` Konrad Rzeszutek Wilk
2016-08-08 6:23 ` Jan Beulich
2016-08-09 18:01 ` Konrad Rzeszutek Wilk
2016-08-10 9:46 ` Jan Beulich
2016-08-11 1:20 ` Konrad Rzeszutek Wilk
2016-08-11 8:52 ` Jan Beulich
2016-08-11 10:56 ` Ian Jackson
2016-08-11 11:13 ` Jan Beulich
2016-08-08 13:42 ` George Dunlap [this message]
2016-08-08 14:01 ` Jan Beulich
2016-08-08 14:10 ` George Dunlap
2016-08-08 15:15 ` Jan Beulich
2016-08-08 16:07 ` Andrew Cooper
2016-08-04 15:49 ` [PATCH v2 2/3] symbols: Generate an xen-sym.map Konrad Rzeszutek Wilk
2016-08-04 19:24 ` Konrad Rzeszutek Wilk
2016-08-05 15:56 ` Jan Beulich
2016-08-04 15:49 ` [PATCH v2 3/3] livepatch: Sync cache of build-id before using it first time Konrad Rzeszutek Wilk
2016-08-05 15:40 ` Jan Beulich
2016-08-05 20:53 ` Konrad Rzeszutek Wilk
2016-08-08 6:26 ` Jan Beulich
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=819874b1-ccdf-9d82-844e-401f63a8daff@citrix.com \
--to=george.dunlap@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=konrad@kernel.org \
--cc=ross.lagerwall@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).