linux-kernel - Re: 2.6.25 and DEBUG_SECTION

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: <480651E2.4060907@gmail.com>
Date:	Wed, 16 Apr 2008 21:22:10 +0200
From:	Jacek Luczak <difrost.kernel@...il.com>
To:	Adrian Bunk <bunk@...nel.org>
CC:	sam@...nborg.org, linux-kbuild@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.25 and DEBUG_SECTION_MISMATCH

Hi Adrian,

> Hi Sam,
> 
> although DEBUG_SECTION_MISMATCH allows to also find exotig things like 
> finding bugs only present when using gcc < 3.4 and CONFIG_HOTPLUG=n at 
> the same time, the problem is that we print
>     WARNING: modpost: Found 13 section mismatch(es).
>     To see full details build your kernel with:
>     'make CONFIG_DEBUG_SECTION_MISMATCH=y'
> but CONFIG_DEBUG_SECTION_MISMATCH is not offered in 2.6.25.

Most of those ,,old mismatches'' where already fixed, so ...

> The options seem to be:
> - going back to the worse but for most practical purposes usable
>   warnings in 2.6.24
> - don't show these warnings during modpost for 2.6.25

... IMO it would be better to not show modpost warnings. It will result in great
number of reports from users. Sam is here a boss.

There's also second part of the story around inline functions which may be
reported while running with CONFIG_DEBUG_SECTION_MISMATCH.

Greats,
	Jacek
--
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/