From: Andrew Morton <akpm@linux-foundation.org>
To: Olaf Hering <olaf@aepfle.de>
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: [PATCH] add hook to read_from_oldmem() to check for non-ram pages
Date: Fri, 6 May 2011 12:55:46 -0700 [thread overview]
Message-ID: <20110506125546.72d138ed.akpm@linux-foundation.org> (raw)
In-Reply-To: <20110506193916.GA26129@aepfle.de>
On Fri, 6 May 2011 21:39:16 +0200
Olaf Hering <olaf@aepfle.de> wrote:
> On Fri, May 06, Andrew Morton wrote:
>
> > So as your module will have a reference to vmcore.c's register and unregister
> > functions, nothing needs to be done: the presence of the client module alone
> > will pin the vmcore.c module.
>
> I meant the other way around. Keep /proc/vmcore open and read from it,
> then try to rmmod foo.ko which provides fn().
>
The client foo.ko will need to prevent itself from being unloaded while
it's actively doing stuff, yes. Typically that would be done in its
module_exit() function - wait for current activity to complete and
block new activity. The "block new activity" thing should be automatic
because nobody has any more references to anything in the module.
next prev parent reply other threads:[~2011-05-06 19:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 9:56 dynamic oldmem in kdump kernel Olaf Hering
2011-04-07 10:23 ` Américo Wang
2011-04-07 13:12 ` Olaf Hering
2011-04-08 10:49 ` Américo Wang
2011-05-02 10:22 ` Olaf Hering
2011-05-03 19:08 ` [PATCH] add hook to read_from_oldmem() to check for non-ram pages Olaf Hering
2011-05-05 21:25 ` Andrew Morton
2011-05-06 10:55 ` Olaf Hering
2011-05-06 19:30 ` Andrew Morton
2011-05-06 19:39 ` Olaf Hering
2011-05-06 19:55 ` Andrew Morton [this message]
2011-05-06 13:20 ` [PATCH v2] " Olaf Hering
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=20110506125546.72d138ed.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
/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