From: Nicolai Stange <nstange@suse.de>
To: JeffleXu <jefflexu@linux.alibaba.com>
Cc: Nicolai Stange <nstange@suse.de>,
jpoimboe@redhat.com, live-patching@vger.kernel.org
Subject: Re: [help] Confusion on livepatch's per-task consistency model
Date: Mon, 02 Mar 2020 17:58:17 +0100 [thread overview]
Message-ID: <87mu8yvgly.fsf@suse.de> (raw)
In-Reply-To: <cd038cf3-4629-6602-1d23-9f0cabb45083@linux.alibaba.com> (jefflexu@linux.alibaba.com's message of "Mon, 2 Mar 2020 21:19:21 +0800")
JeffleXu <jefflexu@linux.alibaba.com> writes:
> So as far as I understand, for all kinds of (data/locking) semantic
> changes, it's the responsibility of the patch writer to detect the
> semantic changes, and usually it can only be analyzed case by
> case. Right?
Exactly :)
Nicolai
--
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg), GF: Felix Imendörffer
prev parent reply other threads:[~2020-03-02 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 8:45 [help] Confusion on livepatch's per-task consistency model JeffleXu
2020-03-02 10:12 ` Petr Mladek
2020-03-02 12:56 ` JeffleXu
2020-03-02 10:36 ` Nicolai Stange
2020-03-02 13:19 ` JeffleXu
2020-03-02 16:58 ` Nicolai Stange [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=87mu8yvgly.fsf@suse.de \
--to=nstange@suse.de \
--cc=jefflexu@linux.alibaba.com \
--cc=jpoimboe@redhat.com \
--cc=live-patching@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 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.