linux-kernel - Re: sections mismatch detection

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100108054144.GA15827@merkur.ravnborg.org>
Date:	Fri, 8 Jan 2010 06:42:14 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	Michal Marek <mmarek@...e.cz>, linux-kbuild@...r.kernel.org,
	Artem Bityutskiy <dedekind1@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: sections mismatch detection

> 
> I would prefer to see (logically) the same section mismatch not be
> reported multiple times, even though they are in different binary
> files.  This would reduce the noise level quite a bit IMO.

That would be nice but is not trivially doable.
We need to discover when there is a section mismatch
resulting from for example a function in kernel/*
calling a function in arch/$ARCH/kernel so we
need to execute the check on multiple levels
i order to catch the bugs as early as possible.

The easy 'fix' would be to execute the check only
on vmlinux.o (default behaviour) but the added
checks with the option enabled allows us to
be much more precise in reporting where
the section mismatch originate from.

	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/