From: "Joseph Reynolds" <jrey@linux.ibm.com>
To: OE-core <openembedded-core@lists.openembedded.org>
Subject: Experiences using livepatch?
Date: Wed, 28 Oct 2020 17:34:00 -0500 [thread overview]
Message-ID: <ae256b5e-012f-26ea-4f91-259a6309b0f1@linux.ibm.com> (raw)
I am re-asking a question from the OpenBMC community.
Does anyone have experience using Linux kernel livepatch with embedded
systems and is willing to share experiences or best practices?
Members of the OpenBMC community discussed a use case that involves many
thousands of systems that all need to be updated as quickly as
possible. Specifically, downloading a new firmware image, performing
firmware update, and rebooting the BMC would be too disruptive and take
too long. The idea is to livepatch the systems as quickly as possible.
The livepatch would be in-memory only and would be followed up with a
normal firmware code update. Details are in the OpenBMC security
working group minutes, referenced below.
We are less interested in the mechanics of building kpatch into the
kernel or in building patches, and more interested in the overall
experience, including how well deploying and applying patches works in
practice.
- Joseph
_________
References:
OpenBMC email:
https://lists.ozlabs.org/pipermail/openbmc/2020-October/023723.html
Discussed in OpenBMC security working group dated 2020-10-28 agenda item 5
https://docs.google.com/document/d/1b7x9BaxsfcukQDqbvZsU2ehMq4xoJRQvLxxsDUWmAOI
BMC firmware code update:
https://github.com/openbmc/docs/blob/master/architecture/code-update/code-update.md
Ubuntu livepatch wiki: https://wiki.ubuntu.com/Kernel/Livepatch.kpatch
Bitbake recipe for livepatch in meta-oe/recipes-kernel/kpatch.
Questions about how to create and apply patches. For example asked
here:
https://stackoverflow.com/questions/34175786/how-to-install-kernel-patch-locally-in-yocto
reply other threads:[~2020-10-28 22:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ae256b5e-012f-26ea-4f91-259a6309b0f1@linux.ibm.com \
--to=jrey@linux.ibm.com \
--cc=openembedded-core@lists.openembedded.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