linux-kernel - Re: Bogus section mismatch errors?

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: <20070508.134101.122616112.davem@davemloft.net>
Date:	Tue, 08 May 2007 13:41:01 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	sam@...nborg.org
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Bogus section mismatch errors?

From: Sam Ravnborg <sam@...nborg.org>
Date: Tue, 8 May 2007 13:52:20 +0200

> There are in slab a function that is not marked __init that refer to a function marked
> __init. But the logic surrounding makes it OK.
> 
> I have no fix/workaround for this.
> Andres has suggested that we should mark functions/data that may refer to __init{data}
> with something like: __nowarn and __nowarndata
> 
> I am planning to implement something so we can mark functions/data with:
> __init_ref_ok and _init_data_ref_ok
> Which is indeed more ugly but expalins what is actually OK.
> 
> I hope to take a look during the weekend.

Thanks for working on this, it's the only mismatch I still see
on sparc64 in current GIT :-)
-
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/