From: Joe Lawrence <joe.lawrence@redhat.com>
To: live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
Jessica Yu <jeyu@kernel.org>, Jiri Kosina <jikos@kernel.org>,
Miroslav Benes <mbenes@suse.cz>, Petr Mladek <pmladek@suse.com>,
Jason Baron <jbaron@akamai.com>,
Evgenii Shatokhin <eshatokhin@virtuozzo.com>
Subject: [PATCH v0 3/3] livepatch: update documentation for shadow variables
Date: Fri, 23 Feb 2018 16:33:50 -0500 [thread overview]
Message-ID: <1519421630-12025-4-git-send-email-joe.lawrence@redhat.com> (raw)
In-Reply-To: <1519421630-12025-1-git-send-email-joe.lawrence@redhat.com>
Update livepatch shadow variable documentation with respect to new
atomic replace / cumulative patch functionality.
Signed-off-by: Joe Lawrence <joe.lawrence@redhat.com>
---
Documentation/livepatch/shadow-vars.txt | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/Documentation/livepatch/shadow-vars.txt b/Documentation/livepatch/shadow-vars.txt
index 89c66634d600..9a2754cf551c 100644
--- a/Documentation/livepatch/shadow-vars.txt
+++ b/Documentation/livepatch/shadow-vars.txt
@@ -179,6 +179,30 @@ doesn't matter what data value the shadow variable holds, its existence
suggests how to handle the parent object.
+Use in cumulative patches
+-------------------------
+
+Cumulative livepatches provide a "one-stop" module containing all active
+livepatch code. A cumulative patch disables and replaces any previously
+loaded livepatch. Shadow variable lifetimes should be carefully
+considered when loading cumulative livepatches:
+
+- If shadow variables lifetimes are specific to livepatch module
+ versions, it may make sense to free them when the corresponding
+ livepatch module is unloaded.
+
+- If shadow variable instances may be safely handled across cumulative
+ livepatch module versions, then it may make sense to free them from
+ unpatch callbacks. When a cumulative patch replaces an existing
+ livepatch, only the cumulative patch's callbacks will be executed.
+ This means that new cumulative livepatches may be loaded while
+ deprecated / disabled livepatches may be unloaded without clearing
+ existing shadow variables.
+
+See Documentation/livepatch/callbacks.txt and cumulative.txt for more
+information on these subjects.
+
+
3. References
=============
--
1.8.3.1
next prev parent reply other threads:[~2018-02-23 21:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 21:33 [PATCH v0 0/3] additional cumulative livepatch doc/samples Joe Lawrence
2018-02-23 21:33 ` [PATCH v0 1/3] livepatch: add sample cumulative patch Joe Lawrence
2018-02-25 1:38 ` Philippe Ombredanne
2018-02-27 11:54 ` Miroslav Benes
2018-03-02 1:19 ` Philippe Ombredanne
2018-03-02 8:31 ` Greg Kroah-Hartman
2018-03-02 9:11 ` Miroslav Benes
2018-02-27 11:37 ` Miroslav Benes
2018-02-23 21:33 ` [PATCH v0 2/3] livepatch: update documentation/samples for callbacks Joe Lawrence
2018-02-27 12:36 ` Miroslav Benes
2018-02-27 14:58 ` Joe Lawrence
2018-02-28 13:20 ` Miroslav Benes
2018-03-02 11:11 ` Petr Mladek
2018-03-02 22:08 ` Joe Lawrence
2018-02-23 21:33 ` Joe Lawrence [this message]
2018-03-02 11:58 ` [PATCH v0 3/3] livepatch: update documentation for shadow variables Petr Mladek
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=1519421630-12025-4-git-send-email-joe.lawrence@redhat.com \
--to=joe.lawrence@redhat.com \
--cc=eshatokhin@virtuozzo.com \
--cc=jbaron@akamai.com \
--cc=jeyu@kernel.org \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.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;
as well as URLs for NNTP newsgroup(s).