xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ross Lagerwall <ross.lagerwall@citrix.com>, Sarah Newman <srn@prgmr.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH LIVEPATCH-BUILD-TOOLS 2/2] Remove section alignment requirement
Date: Fri, 9 Jun 2017 12:38:11 -0400	[thread overview]
Message-ID: <20170609163811.GR8707@char.us.oracle.com> (raw)
In-Reply-To: <20170609160336.13351-2-ross.lagerwall@citrix.com>

On Fri, Jun 09, 2017 at 05:03:36PM +0100, Ross Lagerwall wrote:
> 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.

Why would we have different section aligment for the same twins?

I understand the change here - if for example the original code
had:

 .rodata.str.1

[I think I got the section name right - that should be a string
generated with 1 byte alignment, say 'a'].

But the new patch has a new one:

 .rodata.str.2

['a' -> 'ab']

Is that what we are fixing here?

Also CC-ing Sarah
> 
> 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

  parent reply	other threads:[~2017-06-09 16:38 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 ` [PATCH LIVEPATCH-BUILD-TOOLS 2/2] Remove section alignment requirement Ross Lagerwall
2017-06-09 16:25   ` Andrew Cooper
2017-06-09 16:38   ` Konrad Rzeszutek Wilk [this message]
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=20170609163811.GR8707@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=ross.lagerwall@citrix.com \
    --cc=srn@prgmr.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).