All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Pau Monne <roger.pau@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: konrad.wilk@oracle.com, ross.lagerwall@citrix.com,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: [PATCH 0/9] livepatch-build-tools: some bug fixes and improvements
Date: Mon, 29 Apr 2024 16:56:45 +0200	[thread overview]
Message-ID: <20240429145654.71669-1-roger.pau@citrix.com> (raw)

Hello,

The first 3 patches in the series attempt to fix some bugs, I don't
think they will be specially controversial or difficult to review (patch
1 was already posted standalone).

The rest of the patches are more convoluted, as they attempt to solve
some shortcomings when attempting to create livepatches that change
alternatives or exceptions.  For example a patch that only changes
content in alternative blocks (the code that ends up in the
.altinstr_replacement section) won't work, as create-diff-object will
report that there are no changes.

I've attempted to test as many corner cases as I could come up with, but
it's hard to figure all the possible changes, plus it's also fairly easy
to inadvertently regress existing functionality.

Thanks, Roger.

Roger Pau Monne (9):
  livepatch-build-tools: allow patch file name sizes up to 127
    characters
  create-diff-object: update default alt_instr size
  livepatch-build: fix detection of structure sizes
  create-diff-object: document kpatch_regenerate_special_section()
    behavior
  create-diff-object: move kpatch_include_symbol()
  create-diff-object: detect changes in .altinstr_replacement and .fixup
    sections
  create-diff-object: don't account for changes to .bug_frame.? sections
  create-diff-object: account for changes in the special section itself
  create-diff-object: account for special section changes

 create-diff-object.c | 196 +++++++++++++++++++++++++++++++++----------
 livepatch-build      |  12 ++-
 2 files changed, 161 insertions(+), 47 deletions(-)

-- 
2.44.0



             reply	other threads:[~2024-04-29 15:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29 14:56 Roger Pau Monne [this message]
2024-04-29 14:56 ` [PATCH 1/9] livepatch-build-tools: allow patch file name sizes up to 127 characters Roger Pau Monne
2024-04-29 14:56 ` [PATCH 2/9] create-diff-object: update default alt_instr size Roger Pau Monne
2024-04-29 14:56 ` [PATCH 3/9] livepatch-build: fix detection of structure sizes Roger Pau Monne
2024-04-29 14:56 ` [PATCH 4/9] create-diff-object: document kpatch_regenerate_special_section() behavior Roger Pau Monne
2024-04-29 14:56 ` [PATCH 5/9] create-diff-object: move kpatch_include_symbol() Roger Pau Monne
2024-04-29 14:56 ` [PATCH 6/9] create-diff-object: detect changes in .altinstr_replacement and .fixup sections Roger Pau Monne
2024-04-29 14:56 ` [PATCH 7/9] create-diff-object: don't account for changes to .bug_frame.? sections Roger Pau Monne
2024-04-29 14:56 ` [PATCH 8/9] create-diff-object: account for changes in the special section itself Roger Pau Monne
2024-04-29 14:56 ` [PATCH 9/9] create-diff-object: account for special section changes Roger Pau Monne

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=20240429145654.71669-1-roger.pau@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=ross.lagerwall@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 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.