All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Bohrer <shawn.bohrer@gmail.com>
To: rusty@rustcorp.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: Modversions and long symbol names
Date: Tue, 27 Jan 2009 17:13:51 -0600	[thread overview]
Message-ID: <20090127231351.GA19513@mediacenter> (raw)
In-Reply-To: <20090120173636.GB24529@mediacenter>

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

  reply	other threads:[~2009-01-27 23:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 17:36 Modversions and long symbol names Shawn Bohrer
2009-01-27 23:13 ` Shawn Bohrer [this message]
2009-01-28 13:08 ` Rusty Russell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090127231351.GA19513@mediacenter \
    --to=shawn.bohrer@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.