From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Ross Lagerwall <ross.lagerwall@citrix.com>,
xen-devel@lists.xen.org, Sarah Newman <srn@prgmr.com>
Subject: Re: [PATCH LIVEPATCH-BUILD-TOOLS 2/2] Remove section alignment requirement
Date: Fri, 9 Jun 2017 13:08:32 -0400 [thread overview]
Message-ID: <20170609170831.GS8707@char.us.oracle.com> (raw)
In-Reply-To: <555e0e9c-7ac3-092f-25a5-d57a242e3ffe@citrix.com>
On Fri, Jun 09, 2017 at 06:00:35PM +0100, Andrew Cooper wrote:
> On 09/06/17 17:38, Konrad Rzeszutek Wilk wrote:
> > 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?
>
> Functions also have alignment. For reasons best known to the compiler,
> the fix for XSA-213 caused the alignment of arch_do_multicall_call() to
> change from 1 to 16.
OK, could this be please be included in the commit description?
And with Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Ross, you ok committing it in livepatch-build-tools.git? Thanks!
>
> The build tools choked on this, but the result is legitimate, and did
> work fine.
>
> ~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-06-09 17:08 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
2017-06-09 17:00 ` Andrew Cooper
2017-06-09 17:08 ` Konrad Rzeszutek Wilk [this message]
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=20170609170831.GS8707@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=andrew.cooper3@citrix.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).