From: Prarit Bhargava <prarit@sgi.com>
To: Steve Lord <lord@xfs.org>
Cc: "K.R. Foley" <kr@cybsft.com>, Andrew Morton <akpm@osdl.org>,
pozsy@uhulinux.hu, linux-kernel@vger.kernel.org,
rusty@rustcorp.com.au
Subject: Re: Race condition in module load causing undefined symbols
Date: Tue, 14 Jun 2005 14:23:04 -0400 [thread overview]
Message-ID: <42AF2088.3090605@sgi.com> (raw)
In-Reply-To: <42AF165E.1020702@xfs.org>
Colleagues,
(Copied and edited from a post I made on linux-hotplug-devel last month.)
I've privately emailed Steve with a quick-and-dirty solution for the problems he
was experiencing with the system boot. I wasn't sure if he was having the same
problems I've had with 2.6.12 and old packages but it looks like he was.
I'm surprised we haven't had more people on this list wondering about the
strange behaviour of their initrd/initramfs :) .
When I looked at the original output Steve had posted I noticed that it looked
like drivers were attempting to load at the same time and because of this he
eventually hit an oops. I (and an engineer from another company working on
another arch) have hit the same problem due to the requirements of our current work.
(Unfortunately, I'm more familiar with RedHat/Fedora than I am with other
distro's -- please bear with me.)
The issue is that David Howells posted a patch that changed the behaviour of
kallsyms/insmod/rmmod sometime ago. The patch *is correct* in what it does,
however, the patch requires that /sbin/sh must be aware of pid returns by wait().
http://lkml.org/lkml/2005/1/17/132
There are two fixes that I'm aware of, and depending on what you're doing they
are both "correct" (although in the case of developing in 2.6.12, IMO, you
_must_ do the latter).
The first fix is for the situation where you're developing for a specific
distribution. If this is the case, then you should back out the patch above and
continue moving forward.
The second fix, and again you must do this if you're developing 2.6.12, is to
*update the mkinitrd package* which has a new version of /bin/sh.
P.
next prev parent reply other threads:[~2005-06-14 18:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 14:03 Race condition in module load causing undefined symbols Stephen Lord
2005-06-10 18:25 ` Andrew Morton
2005-06-10 19:06 ` Steve Lord
2005-06-11 3:30 ` Stephen Lord
2005-06-11 8:26 ` Pozsár Balázs
2005-06-11 13:23 ` Steve Lord
2005-06-11 15:05 ` Pozsár Balázs
2005-06-11 17:56 ` Stephen Lord
2005-06-11 19:00 ` Andrew Morton
2005-06-11 19:08 ` Pozsár Balázs
2005-06-11 20:09 ` Steve Lord
2005-06-11 20:18 ` Pozsár Balázs
2005-06-14 13:34 ` Steve Lord
2005-06-14 15:33 ` K.R. Foley
2005-06-14 15:36 ` K.R. Foley
2005-06-14 16:38 ` Steve Lord
2005-06-14 16:56 ` Andi Kleen
2005-06-14 17:16 ` Steve Lord
2005-06-14 20:56 ` Pozsár Balázs
2005-06-14 17:10 ` K.R. Foley
2005-06-14 17:39 ` Steve Lord
2005-06-14 18:23 ` Prarit Bhargava [this message]
2005-06-14 19:27 ` Steve Lord
2005-06-14 19:32 ` Christoph Hellwig
2005-06-14 20:59 ` Pozsár Balázs
2005-06-15 11:28 ` Prarit Bhargava
2005-06-15 11:34 ` Pozsár Balázs
2005-06-15 11:35 ` Prarit Bhargava
2005-06-15 11:43 ` Pozsár Balázs
2005-06-15 12:33 ` Stephen Lord
2005-07-28 19:42 ` David Howells
2005-06-12 6:49 ` 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=42AF2088.3090605@sgi.com \
--to=prarit@sgi.com \
--cc=akpm@osdl.org \
--cc=kr@cybsft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lord@xfs.org \
--cc=pozsy@uhulinux.hu \
--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