From: David Howells <dhowells@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
linuxppc64-dev@ozlabs.org
Subject: Re: [PATCH] Fix kallsyms/insmod/rmmod race
Date: Tue, 18 Jan 2005 19:44:28 +0000 [thread overview]
Message-ID: <1561.1106077468@redhat.com> (raw)
In-Reply-To: <1106014803.30801.22.camel@localhost.localdomain>
Rusty Russell <rusty@rustcorp.com.au> wrote:
> The more I looked at this, the more I warmed to it. I've known for a
> while that people are using kallsyms not for OOPS (eg. /proc/$$/wchan),
> so we should provide a "grabs locks" version, but this solution gets
> around that nicely, while making life more certain for the oops case,
> too.
Hmmm... though it works on i386 SMP, it doesn't, however, seem to work on
ppc64 SMP:-/
My pSeries box seems to think that it can't find any symbols from previously
loaded modules, and my Power5 box is quite happy to load modules that depend
on other modules but panics because it can't mount its root fs.
This is very odd, because the patch is simple enough. Is there anything
obvious I've missed that you can see? Or maybe I'm just misunderstanding how
stop_machine_run() works... maybe it can't be called during initialisation.
David
next prev parent reply other threads:[~2005-01-18 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-17 16:27 [PATCH] Fix kallsyms/insmod/rmmod race David Howells
2005-01-18 2:20 ` Rusty Russell
2005-01-18 19:44 ` David Howells [this message]
2005-01-27 14:02 ` David Howells
2005-01-27 14:08 ` [PATCH] Fix kallsyms/insmod/rmmod race [try #2] David Howells
2005-01-28 0:42 ` Rusty Russell
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=1561.1106077468@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@osdl.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