linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Problem: CONFIG_KALLSYMS is not set + kernel/module.c
Date: Sun, 29 Jul 2012 16:48:11 +0100	[thread overview]
Message-ID: <20120729154811.GF6802@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <50155655.9070002@gmail.com>

This is not ARM specific, please post it more widely.  Also consider
sending it to the person responsible for the module code as listed in
MAINTAINERS.  Thanks.

On Sun, Jul 29, 2012 at 08:27:17AM -0700, Mark Hinds wrote:
>
> In linux-3.2.xx I've been getting kernel dumps when I modprobe some
> modules with CONFIG_KALLSYMS diabled - nls_base.ko for example.
> I traced the problem to kernel/module.c, line 2607 or there about.
>
> Starting with:
> ptr = module_alloc_update_bounds(mod->init_size);
>
> If mod->init_size == 0 then foobar happens. I assume that there is
> no init section in some modules when CONFIG_KALLSYMS is disabled.
>
> Here is my fix:
>
> Index: kernel/module.c
> ===================================================================
> --- kernel/module.c	(.../linux-3.2.24/kernel/module.c)	(revision 9084)
> +++ kernel/module.c	(.../linux-3.2.24-ces/kernel/module.c)	(working copy)
> @@ -2604,20 +2604,24 @@
>  	memset(ptr, 0, mod->core_size);
>  	mod->module_core = ptr;
>
> -	ptr = module_alloc_update_bounds(mod->init_size);
> -	/*
> -	 * The pointer to this block is stored in the module structure
> -	 * which is inside the block. This block doesn't need to be
> -	 * scanned as it contains data and code that will be freed
> -	 * after the module is initialized.
> -	 */
> -	kmemleak_ignore(ptr);
> -	if (!ptr && mod->init_size) {
> -		module_free(mod, mod->module_core);
> -		return -ENOMEM;
> +#warning ### CES/zoro fix problem with mod->init_size == 0
> +	if (mod->init_size) {
> +		ptr = module_alloc_update_bounds(mod->init_size);
> +		/*
> +	 	* The pointer to this block is stored in the module structure
> +	 	* which is inside the block. This block doesn't need to be
> +	 	* scanned as it contains data and code that will be freed
> +	 	* after the module is initialized.
> +	 	*/
> +		kmemleak_ignore(ptr);
> +		if (!ptr) {
> +			module_free(mod, mod->module_core);
> +			return -ENOMEM;
> +		}
> +		memset(ptr, 0, mod->init_size);
> +		mod->module_init = ptr;
>  	}
> -	memset(ptr, 0, mod->init_size);
> -	mod->module_init = ptr;
> +	else mod->module_init = NULL;
>
>  	/* Transfer each section which specifies SHF_ALLOC */
>  	DEBUGP("final section addresses:\n");
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2012-07-29 15:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-29 15:27 Problem: CONFIG_KALLSYMS is not set + kernel/module.c Mark Hinds
2012-07-29 15:48 ` Russell King - ARM Linux [this message]
2012-08-13 10:44 ` Veli-Pekka Peltola

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=20120729154811.GF6802@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).