From: Baoquan He <bhe@redhat.com>
To: Kees Cook <keescook@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Yinghai Lu <yinghai@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Vivek Goyal <vgoyal@redhat.com>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>, Andy Lutomirski <luto@kernel.org>,
lasse.collin@tukaani.org,
Andrew Morton <akpm@linux-foundation.org>,
Dave Young <dyoung@redhat.com>
Subject: Re: [PATCH v3 07/19] x86, kaslr: Get correct max_addr for relocs pointer
Date: Wed, 9 Mar 2016 21:46:12 +0800 [thread overview]
Message-ID: <20160309134612.GE2555@x1.redhat.com> (raw)
In-Reply-To: <CAGXu5jJ=Jdbk90QgEyZG-omQ=vP2EScuLcjZyCF-=_U7tVZ0BA@mail.gmail.com>
On 03/08/16 at 10:16am, Kees Cook wrote:
> On Mon, Mar 7, 2016 at 9:13 PM, Baoquan He <bhe@redhat.com> wrote:
> > On 03/07/16 at 03:16pm, Kees Cook wrote:
> >> On Fri, Mar 4, 2016 at 8:25 AM, Baoquan He <bhe@redhat.com> wrote:
> >> > From: Yinghai Lu <yinghai@kernel.org>
> >> >
> >> > There is boundary checking for pointer in kaslr relocation handling.
> >> >
> >> > Current code is using output_len, and that is VO (vmlinux after objcopy)
> >> > file size plus vmlinux.relocs file size.
> >> >
> >> > That is not right, as we should use loaded address for running.
> >>
> >> I think this needs clarification. If I'm understanding correctly, the
> >> max_addr check should stop at the end of VO, and not include bss, brk,
> >> etc. which follows. In which case, this change is correct: the bounds
> >> checking needed to be tightened.
> >
> > Yes, exactly as you means.
> >
> >>
> >>
> >> >
> >> > At that time parse_elf already move the sections according to ELF headers.
> >> >
> >> > The valid range should be VO [_text, __bss_start) loaded physical addresses.
> >
> > I think it is expressed here. Maybe we can stress it in this patch log.
> > After all it's the main idea of this patch.
> >
> > How about rewriting patch log like this:
> >
> > ********************
> > There is boundary checking for pointer in kaslr relocation handling.
> > However current code is using output_len that is VO (vmlinux after objcopy)
> > file size plus vmlinux.relocs file size to make the valid boundary.
> >
> > That is not right since the max_addr check should stop at the end of VO
> > and excludes bss, brk etc, which follows. Means the valid range should
> > be VO [_text, __bss_start] in loaded physical address space.
> >
> > In this patch, add export for __bss_start to voffset.h and use it to get
> > max_addr.
> > ********************
>
> I would say:
>
> Relocation handling performs bounds checking on the relocated
> addresses. The existing code uses output_len (VO size plus relocs
> size) as the max address. This is not right since the max_addr check
> should stop at the end of VO and exclude bss, brk, etc, which follows.
> The valid range should be VO [_text, __bss_start] in the loaded
> physical address space.
>
> In this patch, add export for __bss_start to voffset.h and use it to
> get the correct max_addr.
Yeah, it's much better. Will use this as patch log.
Thanks!
>
>
> Thanks!
>
> -Kees
>
> >
> >> >
> >> > In the patch, add export for __bss_start to voffset.h and use it to get
> >> > max_addr.
> >> >
> >> > Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> >> > ---
> >> > v2->v3:
> >> > Tune the patch log.
> >> >
> >> > arch/x86/boot/compressed/Makefile | 2 +-
> >> > arch/x86/boot/compressed/misc.c | 2 +-
> >> > 2 files changed, 2 insertions(+), 2 deletions(-)
> >> >
> >> > diff --git a/arch/x86/boot/compressed/Makefile b/arch/x86/boot/compressed/Makefile
> >> > index fef80fa..2e7c0ce 100644
> >> > --- a/arch/x86/boot/compressed/Makefile
> >> > +++ b/arch/x86/boot/compressed/Makefile
> >> > @@ -41,7 +41,7 @@ LDFLAGS_vmlinux := -T
> >> > hostprogs-y := mkpiggy
> >> > HOST_EXTRACFLAGS += -I$(srctree)/tools/include
> >> >
> >> > -sed-voffset := -e 's/^\([0-9a-fA-F]*\) [ABCDGRSTVW] \(_text\|_end\)$$/\#define VO_\2 _AC(0x\1,UL)/p'
> >> > +sed-voffset := -e 's/^\([0-9a-fA-F]*\) [ABCDGRSTVW] \(_text\|__bss_start\|_end\)$$/\#define VO_\2 _AC(0x\1,UL)/p'
> >> >
> >> > quiet_cmd_voffset = VOFFSET $@
> >> > cmd_voffset = $(NM) $< | sed -n $(sed-voffset) > $@
> >> > diff --git a/arch/x86/boot/compressed/misc.c b/arch/x86/boot/compressed/misc.c
> >> > index 069120e..dd7ed8a 100644
> >> > --- a/arch/x86/boot/compressed/misc.c
> >> > +++ b/arch/x86/boot/compressed/misc.c
> >> > @@ -259,7 +259,7 @@ static void handle_relocations(void *output, unsigned long output_len)
> >> > int *reloc;
> >> > unsigned long delta, map, ptr;
> >> > unsigned long min_addr = (unsigned long)output;
> >> > - unsigned long max_addr = min_addr + output_len;
> >> > + unsigned long max_addr = min_addr + (VO___bss_start - VO__text);
> >> >
> >> > /*
> >> > * Calculate the delta between where vmlinux was linked to load
> >> > --
> >> > 2.5.0
> >> >
> >>
> >>
> >>
> >> --
> >> Kees Cook
> >> Chrome OS & Brillo Security
>
>
>
> --
> Kees Cook
> Chrome OS & Brillo Security
next prev parent reply other threads:[~2016-03-09 13:46 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 16:24 [PATCH v3 00/19] x86, boot: kaslr cleanup and 64bit kaslr support Baoquan He
2016-03-04 16:24 ` [PATCH v3 01/19] x86, kaslr: Remove not needed parameter for choose_kernel_location Baoquan He
2016-03-07 22:28 ` Kees Cook
2016-03-04 16:25 ` [PATCH v3 02/19] x86, boot: Move compressed kernel to end of buffer before decompressing Baoquan He
2016-03-07 22:35 ` Kees Cook
2016-03-08 4:50 ` Baoquan He
2016-03-04 16:25 ` [PATCH v3 03/19] x86, boot: Move z_extract_offset calculation to header.S Baoquan He
2016-03-04 16:25 ` [PATCH v3 04/19] x86, kaskr: Update the description for decompressor worst case Baoquan He
2016-03-04 16:25 ` [PATCH v3 05/19] x86, boot: Fix run_size calculation Baoquan He
2016-03-07 23:10 ` Kees Cook
2016-03-08 4:57 ` Baoquan He
2016-03-08 18:05 ` Kees Cook
2016-03-04 16:25 ` [PATCH v3 06/19] x86, kaslr: Clean up useless code related to run_size Baoquan He
2016-03-07 23:12 ` Kees Cook
2016-03-08 5:00 ` Baoquan He
2016-03-04 16:25 ` [PATCH v3 07/19] x86, kaslr: Get correct max_addr for relocs pointer Baoquan He
2016-03-07 23:16 ` Kees Cook
2016-03-08 5:13 ` Baoquan He
2016-03-08 18:16 ` Kees Cook
2016-03-09 13:46 ` Baoquan He [this message]
2016-03-04 16:25 ` [PATCH v3 08/19] x86, kaslr: Consolidate mem_avoid array filling Baoquan He
2016-03-07 23:28 ` Kees Cook
2016-03-08 5:21 ` Baoquan He
2016-03-08 18:17 ` Kees Cook
2016-03-09 13:42 ` Baoquan He
2016-03-04 16:25 ` [PATCH v3 09/19] x86, boot: Split kernel_ident_mapping_init to another file Baoquan He
2016-03-04 16:25 ` [PATCH v3 10/19] x86, 64bit: Set ident_mapping for kaslr Baoquan He
2016-03-07 23:34 ` Kees Cook
2016-03-08 5:25 ` Baoquan He
2016-03-21 7:50 ` Baoquan He
2016-03-21 19:48 ` Kees Cook
2016-03-04 16:25 ` [PATCH v3 11/19] x86, boot: Add checking for memcpy Baoquan He
2016-03-07 23:36 ` Kees Cook
2016-03-08 5:30 ` Baoquan He
2016-03-04 16:25 ` [PATCH v3 12/19] x86, kaslr: Fix a bug that relocation can not be handled when kernel is loaded above 2G Baoquan He
2016-03-07 23:30 ` Kees Cook
2016-03-08 5:22 ` Baoquan He
2016-03-04 16:25 ` [PATCH v3 13/19] x86, kaslr: Introduce struct slot_area to manage randomization slot info Baoquan He
2016-03-04 16:25 ` [PATCH v3 14/19] x86, kaslr: Add two functions which will be used later Baoquan He
2016-03-04 16:25 ` [PATCH v3 15/19] x86, kaslr: Introduce fetch_random_virt_offset to randomize the kernel text mapping address Baoquan He
2016-03-04 16:25 ` [PATCH v3 16/19] x86, kaslr: Randomize physical and virtual address of kernel separately Baoquan He
2016-03-07 23:51 ` Kees Cook
2016-03-08 5:34 ` Baoquan He
2016-03-08 18:24 ` Kees Cook
2016-03-09 13:40 ` Baoquan He
2016-03-09 18:07 ` Kees Cook
2016-03-10 15:15 ` Baoquan He
2016-03-04 16:25 ` [PATCH v3 17/19] x86, kaslr: Add support of kernel physical address randomization above 4G Baoquan He
2016-03-04 16:25 ` [PATCH v3 18/19] x86, kaslr: Remove useless codes Baoquan He
2016-03-04 16:25 ` [PATCH v3 19/19] x86, kaslr: Allow random address to be below loaded address Baoquan He
2016-03-05 11:35 ` [PATCH v3 00/19] x86, boot: kaslr cleanup and 64bit kaslr support Baoquan He
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=20160309134612.GE2555@x1.redhat.com \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=lasse.collin@tukaani.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=vgoyal@redhat.com \
--cc=yinghai@kernel.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).