From: Rusty Russell <rusty@rustcorp.com.au>
To: Keith Owens <kaos@ocs.com.au>
Cc: pazke@orbita1.ru, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] __init and friends support for loadable modules
Date: Thu, 9 May 2002 17:45:50 +1000 [thread overview]
Message-ID: <20020509174550.79d08e5b.rusty@rustcorp.com.au> (raw)
In-Reply-To: <9276.1020866527@ocs3.intra.ocs.com.au>
On Thu, 09 May 2002 00:02:07 +1000
Keith Owens <kaos@ocs.com.au> wrote:
> On Wed, 8 May 2002 14:29:33 +0400,
> Andrey Panin <pazke@orbita1.ru> wrote:
> >attached patch adds support for freeing .init sections of loadable modules
> >after init_module() function exits. Modutils have support for this since 19=
> >98,
> >but kernel support didn't exist.
>
> The main reason I have not done this myself is the interaction between
> freeing code areas and the exception and unwind tables. When you free
> code, you should remove or nullify the related unwind and exception
> entries. Another module could be loaded into the area that used to
> contain init code and it would then be mapped by the first module's
> tables, oops.
Excellent catch, Keith. I missed this in my current implementation, and
will have to patch the exception tables in the init release callback. I
also get around this because I allow archs to refuse to have separate
init and core sections if they want.
BTW, I just got ppc64 in-kernel relocations working. I am starting on
ia64, in the theory that if you can do ia64, you can do anything.
Cheers,
Rusty.
--
there are those who do and those who hang on and you don't see too
many doers quoting their contemporaries. -- Larry McVoy
prev parent reply other threads:[~2002-05-09 7:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-08 10:29 [PATCH][RFC] __init and friends support for loadable modules Andrey Panin
2002-05-08 14:02 ` Keith Owens
2002-05-09 7:45 ` Rusty Russell [this message]
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=20020509174550.79d08e5b.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pazke@orbita1.ru \
/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.