From: Rusty Russell <rusty@rustcorp.com.au>
To: Tom Rini <trini@kernel.crashing.org>
To: 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>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] 2.6 && module + -g && kernel w/o -g
Date: Thu, 15 Jan 2004 10:00:11 +1100 [thread overview]
Message-ID: <20040115013723.29B912C0DC@lists.samba.org> (raw)
In-Reply-To: Your message of "Wed, 14 Jan 2004 14:09:37 PDT." <20040114210937.GA983@stop.crashing.org>
In message <20040114210937.GA983@stop.crashing.org> you write:
> Okay. I've been looking at stock 2.6.1 noticed that the fix for this
> issue that Rusty proposed, and that ultimately made it into 2.6.1-rc3
> (or so) is not correct. The problem is that we do:
>
> err = module_frob_arch_sections(hdr, sechdrs, secstrings, mod);
> /* Which goes over every .debug section and can take _ages_ on something
> * like ipv6 */
Right. So the arch-specific module_frob_arch_sections() can be slow.
Logically, the fix should be in those module_frob_arch_sections(), not
in the generic code.
> + /* If we find any debug RELAs, frob these away now. */
> + if (sechdrs[i].sh_type == SHT_RELA &&
> + (strstr(secstrings+sechdrs[i].sh_name, ".debug")
> + != 0))
> + sechdrs[i].sh_type = SHT_NULL;
> +
Doesn't cover SHT_REL, and I really dislike name matches: they've bitten
us before.
Really, I prefer the arch-specific optimization.
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2004-01-15 1:39 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 ` Tom Rini
2004-01-14 22:23 ` David Mosberger
2004-01-14 22:33 ` Tom Rini
2004-01-14 23:00 ` Rusty Russell [this message]
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=20040115013723.29B912C0DC@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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
Powered by JetHome