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: <20080416192306.GA3090@uranus.ravnborg.org>
Date:	Wed, 16 Apr 2008 21:23:06 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: 2.6.25 and DEBUG_SECTION_MISMATCH

Hi Adrian.

On Wed, Apr 16, 2008 at 08:51:35PM +0300, Adrian Bunk wrote:
> 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'

So we print exact instructions how to get more info.
And several people has posted list of section mismatch warnings recently,
so the instructions are understood.
I fail to see any problem with that.

Obviously it would be better if we bailed out with a big fat warning
if someone _adds_ a new section mismatch warning.

> but CONFIG_DEBUG_SECTION_MISMATCH is not offered in 2.6.25.
If you by "not offered" try to say that the CONFIG option
is not available in kconfig then you are correct.
But you are in the instructions above asked to supply it
on the command line to make - not to enable it in the
kconfig configuration.

I would prefer we were down to less than 5 warnings so we could
enable it in kconfig but maybe after next merge window.

	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/