mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [patch] scheduler fixes, 2.5.32-BK
Date: Fri, 30 Aug 2002 01:12:38 -0700	[thread overview]
Message-ID: <3D6F28F6.71228222@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0208300948320.8448-100000@localhost.localdomain>

Ingo Molnar wrote:
> 
> >  - changes the migration code to use struct completion. Andrew pointed out
> >    that there might be a small window in where the up() touches the
> >    semaphore while the waiting task goes on and frees its stack. And
> >    completion is more suited for this kind of stuff anyway.
> 
> actually, i think the race does not exist. up() is perfectly safely done
> on the on-stack semaphore, because both the wake_up() done by __up() and
> the __down() path takes the waitqueue spinlock, so i cannot see where the
> up() touches the semaphore after the down()-ed task has been woken up.
> 

yep, looks like the killing of the semaphore_lock made the race
go away.

But ia64, sparc and x86_64 use semaphore_lock, so they still are
exposed.

  reply	other threads:[~2002-08-30  7:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-30  7:43 Ingo Molnar
2002-08-30  7:55 ` Ingo Molnar
2002-08-30  8:12   ` Andrew Morton [this message]
2002-08-30  8:22     ` Ingo Molnar
2002-08-30 17:03   ` Linus Torvalds
2002-08-30 17:05     ` Ingo Molnar
2002-08-30 17:16       ` Ingo Molnar
2002-08-30 17:19       ` Linus Torvalds
2002-08-30 17:28         ` Ingo Molnar
2002-08-30 17:47           ` Linus Torvalds
2002-08-30 18:05             ` Ingo Molnar

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=3D6F28F6.71228222@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@transmeta.com \
    /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

all inboxes | Powered by JetHome®