linux-kernel - Re: Modversions and long symbol names

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]

Date:	Tue, 27 Jan 2009 17:13:51 -0600
From:	Shawn Bohrer <shawn.bohrer@...il.com>
To:	rusty@...tcorp.com.au
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Modversions and long symbol names

On Tue, Jan 20, 2009 at 11:36:36AM -0600, Shawn Bohrer wrote:
> Currently when modversions is enabled the kernel will not load any
> modules that depend on exported symbols with names longer than
> 64 - sizeof(unsigned long) characters.
> 
> This is because the struct modversion_info has the name member set to a
> size of MODULE_NAME_LEN.  This is not the module name this is the symbol
> name so I'm guessing this is a mistake or at least a misused constant.
> 
> Is it possible to increase this size to something more reasonable like
> 512 characters?

Hopefully everyone is back from linux.conf.au and is caught up on email
now.  Is there a reason modversions imposes this small symbol name
length?  Unfortunately I have modules that have longer exported symbol
names and this prevents them from loading on kernels that have
modversions enabled.  Of course they load just fine when modversions is
disabled.  I can't just shorten my symbol names because they are
exported and other modules are using them.

--
Shawn
--
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/