public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bob Miller <rem@osdl.org>
To: Ron Niles <Ron.Niles@falconstor.com>
Cc: David Woodhouse <dwmw2@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: Oops from local semaphore race condition
Date: Tue, 21 May 2002 14:16:14 -0700	[thread overview]
Message-ID: <20020521141614.A13087@doc.pdx.osdl.net> (raw)
In-Reply-To: <E79B8AB303080F4096068F046CD1D89B934D5E@exchange1.FalconStor.Net>

On Tue, May 21, 2002 at 03:41:19PM -0400, Ron Niles wrote:
> 
> 
> Ron.Niles@falconstor.com said:
> >> Then I realized it can possibly go corrupt, due to a race condition
> >> which lets down() continue before up() is complete:
> 
> From: David Woodhouse [mailto:dwmw2@infradead.org]
> 
> >This is what completions were added for.
> 
> Thanks, struct completion is the best way; it's gonna be tough to maintain
> backward compatibility though.
> 
> One comment; it looks like the implementation in sched.c should more
> properly be using wq_write_lock_irqsave on the lock.
> 
I sent patches to Linus to fix this back in February.  Dave Jones picked
them up and they are still in his tree.  I don't know when/if he is going
to forward them onto Linus for inclusion into his tree.

-- 
Bob Miller					Email: rem@osdl.org
Open Source Development Lab			Phone: 503.626.2455 Ext. 17

  reply	other threads:[~2002-05-21 21:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-21 19:41 Oops from local semaphore race condition Ron Niles
2002-05-21 21:16 ` Bob Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-21  0:11 Ron Niles
2002-05-21 12:26 ` David Woodhouse

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=20020521141614.A13087@doc.pdx.osdl.net \
    --to=rem@osdl.org \
    --cc=Ron.Niles@falconstor.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.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