linux-kernel - Re: kbuild: fix section mismatch check for vmlinux

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 11 Jun 2007 23:50:52 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Jan Beulich <jbeulich@...ell.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: kbuild: fix section mismatch check for vmlinux

On Mon, Jun 11, 2007 at 10:25:59AM +0200, Jan Beulich wrote:
> >vmlinux does not contain relocation entries which is
> >used by the section mismatch checks.
> >Reported by: Atsushi Nemoto <anemo@....ocn.ne.jp>
> >
> >Use the individual objects as inputs to overcome
> >this limitation.
> >In modpost check the .o files and skip non-ELF files.
> >
> >Signed-off-by: Sam Ravnborg <sam@...nborg.org>
> 
> This still doesn't appear to catch all cases - since the checking logic works
> on a per-module basis, references between the individual .o files aren't
> being checked. A current instance where this is visible is x86-64's recently
> added alloc_bootmem_high_node (non-__init, in arch/x86_64/mm/built-in.o)
> calling __alloc_bootmem_core (__init, in mm/built-in.o). I suppose there's
> no way around linking $(KBUILD_VMLINUX_OBJS) into vmlinux.o, and
> checking that file instead.

It is planned to do something around these lines.
Today we do a lot of linking in the final stages and the Makefile
magic involved is starting to make my head spinning.
So my plan is to redo all the "link vmlinux" stuff and
locate it in the top-level Kbuild file.
As part of this process I would then create vmlinux.o as one
of the steps - it will have all sections intact and allow
for a full modpost run.

We would then lack the hint about what subsystem caused the
warning bot most often a "git grep" tells me that in less than 10
seconds anyway.

The extra link step would also benefit kallsyms check I think so
it will not be waste of time.

But summer has hit us so it may be after next merge window.
The changes would anyway need to cook in -mm a while before
I would push them to mainstream.

	Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/