All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Lord <lord@xfs.org>
To: Andrew Morton <akpm@osdl.org>
Cc: "Pozsár Balázs" <pozsy@uhulinux.hu>,
	linux-kernel@vger.kernel.org, rusty@rustcorp.com.au
Subject: Re: Race condition in module load causing undefined symbols
Date: Sat, 11 Jun 2005 08:23:20 -0500	[thread overview]
Message-ID: <42AAE5C8.9060609@xfs.org> (raw)
In-Reply-To: <20050611082642.GB17639@ojjektum.uhulinux.hu>

Pozsár Balázs wrote:
> On Fri, Jun 10, 2005 at 11:25:15AM -0700, Andrew Morton wrote:
> 
>>I wonder if rather than the intermittency being time-based, it is
>>load-address-based?  For example, suppose there's a bug in the symbol
>>lookup code?
> 
> 
> Just a data point: I met the same problem with 2.6.12-rc5, using
> gcc 3.3.4.
> I think it's time-based issue, because I was playing around with the 
> initscripts, and the bug shows up when there are lots of modprobes in a 
> short time.
> 
>

I think this is not actually module loading itself, but a problem
between the fork/exec/wait code in nash and the kernel. The
commands which have problems are the ones which are not built
into nash. So this looks more like a problem with wait. This
would explain sleep fixing it and the fact that I have device
issues after module load.

Steve

  reply	other threads:[~2005-06-11 13:23 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 [this message]
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
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=42AAE5C8.9060609@xfs.org \
    --to=lord@xfs.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.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 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.