mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: mbm@mort.demon.co.uk
To: "Petr Vandrovec" <vandrove@vc.cvut.cz>, rusty@rustcorp.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.48: BUG() at kernel/module.c:1000
Date: Mon, 18 Nov 2002 22:39:11 +0000 (GMT)	[thread overview]
Message-ID: <200211182239.gAIMdBL04074@mort.demon.co.uk> (raw)
In-Reply-To: <20021118192001.21441.11326.Mailman@lists.us.dell.com> from "linux-kernel-digest-request@lists.us.dell.com" at Nov 18, 2002 01:20:01

> Date: Mon, 18 Nov 2002 19:06:56 +0100
> From: Petr Vandrovec <vandrove@vc.cvut.cz>
> To: rusty@rustcorp.com.au
> Cc: linux-kernel@vger.kernel.org
> Subject: 2.5.48: BUG() at kernel/module.c:1000
> 
> Hi Rusty,
>   I'm trying to get VMware working, and unfortunately new insmod
> is not able to load generated module. It died at line 1000 of 
> kernel/module.c, because of used.core_size > mod->core_size:
>      INIT=0/0  CORE=34252/34228

Hi,

This appears to be due to the COMMON symbol "errno".

The code (get_sizes) that calculates the amount of space required
by the sections assumes that the first one is loaded at address
zero (or large alignment) when performing subsequent alignments.

Unfortunately, this is not the case when the actual load takes
place because the common area (length common_length) is allocated
first.  This needs to be rounded up to the strictest alignment of
any of the ALLOC sections before the copies start.  (Hence the
difference of (2**5 - 8) which is apparent in the CORE values above.)

cheers,

-Malcolm


       reply	other threads:[~2002-11-18 22:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20021118192001.21441.11326.Mailman@lists.us.dell.com>
2002-11-18 22:39 ` mbm [this message]
2002-11-18 23:50   ` Rusty Russell
2002-11-19 11:54     ` Petr Vandrovec
2002-11-20  6:54       ` Rusty Russell
2002-11-18 18:06 Petr Vandrovec

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=200211182239.gAIMdBL04074@mort.demon.co.uk \
    --to=mbm@mort.demon.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbm@tinc.org.uk \
    --cc=rusty@rustcorp.com.au \
    --cc=vandrove@vc.cvut.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®