From: Ross Lagerwall <ross.lagerwall@citrix.com>
To: xen-devel@lists.xen.org
Cc: Ross Lagerwall <ross.lagerwall@citrix.com>
Subject: [PATCH LIVEPATCH-BUILD-TOOLS 2/2] Remove section alignment requirement
Date: Fri, 9 Jun 2017 17:03:36 +0100 [thread overview]
Message-ID: <20170609160336.13351-2-ross.lagerwall@citrix.com> (raw)
In-Reply-To: <20170609160336.13351-1-ross.lagerwall@citrix.com>
Remove the requirement that section twins have the same alignment. The
section alignment of the patched section is respected by the loader in
Xen so it shouldn't matter if the original section alignment was
different.
Signed-off-by: Ross Lagerwall <ross.lagerwall@citrix.com>
---
create-diff-object.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/create-diff-object.c b/create-diff-object.c
index ba19daf..82f777e 100644
--- a/create-diff-object.c
+++ b/create-diff-object.c
@@ -754,7 +754,6 @@ static void kpatch_compare_correlated_section(struct section *sec)
if (sec1->sh.sh_type != sec2->sh.sh_type ||
sec1->sh.sh_flags != sec2->sh.sh_flags ||
sec1->sh.sh_addr != sec2->sh.sh_addr ||
- sec1->sh.sh_addralign != sec2->sh.sh_addralign ||
sec1->sh.sh_entsize != sec2->sh.sh_entsize)
DIFF_FATAL("%s section header details differ", sec1->name);
--
2.9.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-06-09 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 16:03 [PATCH LIVEPATCH-BUILD-TOOLS 1/2] Ignore .discard sections Ross Lagerwall
2017-06-09 16:03 ` Ross Lagerwall [this message]
2017-06-09 16:25 ` [PATCH LIVEPATCH-BUILD-TOOLS 2/2] Remove section alignment requirement Andrew Cooper
2017-06-09 16:38 ` Konrad Rzeszutek Wilk
2017-06-09 17:00 ` Andrew Cooper
2017-06-09 17:08 ` Konrad Rzeszutek Wilk
2017-06-12 7:30 ` Ross Lagerwall
2017-06-09 16:25 ` [PATCH LIVEPATCH-BUILD-TOOLS 1/2] Ignore .discard sections Andrew Cooper
2017-06-09 16:35 ` Konrad Rzeszutek Wilk
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=20170609160336.13351-2-ross.lagerwall@citrix.com \
--to=ross.lagerwall@citrix.com \
--cc=xen-devel@lists.xen.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).