From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Ross Lagerwall <ross.lagerwall@citrix.com>,
Julien Grall <julien.grall@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Jan Beulich <JBeulich@suse.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 1/2] xen/livepatch: Clean up arch relocation handling
Date: Mon, 19 Jun 2017 14:18:25 -0400 [thread overview]
Message-ID: <20170619181825.GA21025@char.us.oracle.com> (raw)
In-Reply-To: <26463217-0fb5-efe3-bb72-cf39dc8a3554@citrix.com>
On Wed, Jun 14, 2017 at 07:28:39PM +0100, Andrew Cooper wrote:
> On 14/06/17 15:02, Jan Beulich wrote:
> >>>> On 14.06.17 at 15:44, <konrad.wilk@oracle.com> wrote:
> >> On Tue, Jun 13, 2017 at 09:51:35PM +0100, Andrew Cooper wrote:
> >>> --- a/xen/arch/arm/arm32/livepatch.c
> >>> +++ b/xen/arch/arm/arm32/livepatch.c
> >>> @@ -224,21 +224,21 @@ int arch_livepatch_perform(struct livepatch_elf *elf,
> >>> const struct livepatch_elf_sec *rela,
> >>> bool use_rela)
> >>> {
> >>> - const Elf_RelA *r_a;
> >>> - const Elf_Rel *r;
> >>> - unsigned int symndx, i;
> >>> - uint32_t val;
> >>> - void *dest;
> >>> + unsigned int i;
> >>> int rc = 0;
> >>>
> >>> for ( i = 0; i < (rela->sec->sh_size / rela->sec->sh_entsize); i++ )
> >>> {
> >>> + unsigned int symndx;
> >>> + uint32_t val;
> >>> + void *dest;
> >>> unsigned char type;
> >>> - s32 addend = 0;
> >>> + s32 addend;
> >>>
> >>> if ( use_rela )
> >>> {
> >>> - r_a = rela->data + i * rela->sec->sh_entsize;
> >>> + const Elf_RelA *r_a = rela->data + i * rela->sec->sh_entsize;
> >>> +
> >>> symndx = ELF32_R_SYM(r_a->r_info);
> >>> type = ELF32_R_TYPE(r_a->r_info);
> >>> dest = base->load_addr + r_a->r_offset; /* P */
> >>> @@ -246,10 +246,12 @@ int arch_livepatch_perform(struct livepatch_elf *elf,
> >>> }
> >>> else
> >>> {
> >>> - r = rela->data + i * rela->sec->sh_entsize;
> >>> + const Elf_Rel *r = rela->data + i * rela->sec->sh_entsize;
> >>> +
> >>> symndx = ELF32_R_SYM(r->r_info);
> >>> type = ELF32_R_TYPE(r->r_info);
> >>> dest = base->load_addr + r->r_offset; /* P */
> >>> + addend = get_addend(type, dest);
> >>> }
> >>>
> >>> if ( symndx > elf->nsym )
> >>> @@ -259,13 +261,11 @@ int arch_livepatch_perform(struct livepatch_elf *elf,
> >>> return -EINVAL;
> >>> }
> >>>
> >>> - if ( !use_rela )
> >>> - addend = get_addend(type, dest);
> >> This was added right after the symndx > elf->nsym check as
> >> way to make sure we won't dereference the dest (b/c the symbol
> >> may be outside the bounds).
> > But symndx isn't being used here.
>
> Indeed. r->r_offset (and therefore dest) has no direct bearing on symndx.
/me nods.
>
> Having said that, there is no sanity check that r->r_offset is within
> base->load_addr + sec->sh_size in arm32, whereas both arm64 and x86
> appear to do this check.
True.
And the tricky part (it was to me at least) was that ARM32 is all
REL and not RELA so the opcode gets modified after the operation.
Which means it gets a bit complex to add a boundary check in
'get_addend' .
Hm, it would seem the best way is to add a
if ( r->r_offset >= base->sec->sh_size ||
(r->r_offset + sizeof(uint32_t)) > base->sec->sh_size )
that is common for use_rela and not.
Anyhow I can do that as I would want to check this
on real hardware :-)
For your patch (as is)
Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Are you OK committing it in?
>
> ~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-06-19 18:18 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 20:51 [PATCH 1/2] xen/livepatch: Clean up arch relocation handling Andrew Cooper
2017-06-13 20:51 ` [PATCH 2/2] xen/livepatch: Don't crash on encountering STN_UNDEF relocations Andrew Cooper
2017-06-13 21:13 ` Andrew Cooper
2017-06-14 10:03 ` Jan Beulich
2017-06-14 10:11 ` Jan Beulich
2017-06-14 10:13 ` Andrew Cooper
2017-06-14 10:24 ` Jan Beulich
2017-06-14 14:18 ` Konrad Rzeszutek Wilk
2017-06-14 18:33 ` Andrew Cooper
2017-06-14 18:49 ` Jan Beulich
2017-06-19 18:30 ` Konrad Rzeszutek Wilk
2017-06-19 23:05 ` Andrew Cooper
2017-06-20 7:15 ` Jan Beulich
2017-06-20 13:30 ` Konrad Rzeszutek Wilk
2017-06-14 19:08 ` Konrad Rzeszutek Wilk
2017-06-21 18:13 ` [PATCH for-4.9 v2] " Andrew Cooper
2017-06-22 1:26 ` Konrad Rzeszutek Wilk
2017-06-22 15:27 ` Konrad Rzeszutek Wilk
2017-06-22 16:10 ` Konrad Rzeszutek Wilk
2017-06-22 16:33 ` Konrad Rzeszutek Wilk
2017-06-22 17:05 ` Konrad Rzeszutek Wilk
2017-06-23 9:44 ` Jan Beulich
2017-06-22 7:40 ` Jan Beulich
2017-06-22 9:49 ` Ross Lagerwall
2017-06-14 9:25 ` [PATCH 1/2] xen/livepatch: Clean up arch relocation handling Jan Beulich
2017-06-14 13:44 ` Konrad Rzeszutek Wilk
2017-06-14 14:02 ` Jan Beulich
2017-06-14 18:28 ` Andrew Cooper
2017-06-19 18:18 ` Konrad Rzeszutek Wilk [this message]
2017-06-20 7:36 ` Jan Beulich
2017-06-20 7:39 ` Andrew Cooper
2017-06-20 7:41 ` Andrew Cooper
2017-06-20 7:56 ` Jan Beulich
2017-06-20 13:36 ` Konrad Rzeszutek Wilk
2017-06-22 1:27 ` Is [PATCH for-4.9] Was:Re: " 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=20170619181825.GA21025@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=julien.grall@arm.com \
--cc=ross.lagerwall@citrix.com \
--cc=sstabellini@kernel.org \
--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).