public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: davidm@hpl.hp.com
Cc: Paul Mackerras <paulus@samba.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Christoph Hellwig <hch@infradead.org>,
	Andrew Morton <akpm@osdl.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] 2.6 && module + -g && kernel w/o -g
Date: Wed, 14 Jan 2004 15:33:48 -0700	[thread overview]
Message-ID: <20040114223348.GC983@stop.crashing.org> (raw)
In-Reply-To: <16389.49505.481834.12558@napali.hpl.hp.com>

On Wed, Jan 14, 2004 at 02:23:29PM -0800, David Mosberger wrote:
> >>>>> On Wed, 14 Jan 2004 14:09:37 -0700, Tom Rini <trini@kernel.crashing.org> said:
> 
>   Tom> The following patch fixes the problem for me on PPC32:
> 
>   Tom> --- 1.96/kernel/module.c	Wed Jan  7 22:46:59 2004
>   Tom> +++ edited/kernel/module.c	Wed Jan 14 14:05:12 2004
>   Tom> @@ -1439,6 +1439,13 @@
>   Tom> strindex = sechdrs[i].sh_link;
>   Tom> strtab = (char *)hdr + sechdrs[strindex].sh_offset;
>   Tom> }
>   Tom> +
>   Tom> +		/* If we find any debug RELAs, frob these away now. */
>   Tom> +		if (sechdrs[i].sh_type == SHT_RELA &&
>   Tom> +				(strstr(secstrings+sechdrs[i].sh_name, ".debug")
>   Tom> +				 != 0))
>   Tom> +			sechdrs[i].sh_type = SHT_NULL;
>   Tom> +
>   Tom> #ifndef CONFIG_MODULE_UNLOAD
>   Tom> /* Don't load .exit sections */
>   Tom> if (strncmp(secstrings+sechdrs[i].sh_name, ".exit", 5) == 0)
> 
>   Tom> IMHO, this shouldn't be covered under a PPC32 test since at
>   Tom> least PPC32, PPC64 and Alpha have this issue, and I suspect
>   Tom> that ia64, parisc, s390 and v850 have the problem as well
>   Tom> (based on what their module_arch_frob bits look to be doing).
> 
> As far as ia64 is concerned, adding a check for .debug should be OK,
> but since the debug sections do not have any relocs anyhow, it
> shouldn't make much of a difference one way or another (addresses in
> the debug section a segment-relative).

OK, I wasn't sure.  I just did a real quick skim of everyones module.c
to see if they did any for loops and checking of SHT_RELA.

-- 
Tom Rini
http://gate.crashing.org/~trini/

  reply	other threads:[~2004-01-14 22:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040108003040.GA18481@stop.crashing.org>
2004-01-14 21:09 ` [PATCH][RFC] 2.6 && module + -g && kernel w/o -g Tom Rini
2004-01-14 22:23   ` David Mosberger
2004-01-14 22:33     ` Tom Rini [this message]
2004-01-14 23:00   ` Rusty Russell
2004-01-15 15:38     ` Tom Rini

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=20040114223348.GC983@stop.crashing.org \
    --to=trini@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=davidm@hpl.hp.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox