Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Kaz Kylheku <kaz@zeugmasystems.com>, linux-mips@linux-mips.org
Subject: Re: futex_wake_op deadlock?
Date: Tue, 20 Nov 2007 10:29:47 -0800	[thread overview]
Message-ID: <4743279B.7070402@avtrex.com> (raw)
In-Reply-To: <20071120112051.GB30675@linux-mips.org>

Ralf Baechle wrote:

> 
> Notice the branch at the end of the fixup code, it goes back to the
> SC instruction.  The SC instruction took an exception so it will not have
> changed $1 so the loop will continue endless unless by coincidence the
> value to be stored from $1 happened to be zero.
> 
> Obviously this one was MIPS specific and may hit all supported ABIs.  So
> my initial suspicion this might be the issue David Miller recently
> discovered in the binary compat code isn't true.  And it's a local DoS
> probably for all of 2.6.16 and up.
> 

I mostly similar code is in 2.6.15, so I think it is effected as well. 
2.6.12 on the other hand doesn't seem to have futex.h

David Daney

  parent reply	other threads:[~2007-11-20 18:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-16 23:52 futex_wake_op deadlock? Kaz Kylheku
2007-11-16 23:52 ` Kaz Kylheku
2007-11-19 18:48 ` Ralf Baechle
2007-11-19 21:27   ` Kaz Kylheku
2007-11-19 21:27     ` Kaz Kylheku
2007-11-19 21:42     ` Kaz Kylheku
2007-11-19 21:42       ` Kaz Kylheku
2007-11-20 11:21     ` Ralf Baechle
2007-11-20 18:06       ` Kaz Kylheku
2007-11-20 18:06         ` Kaz Kylheku
2007-11-20 18:16         ` Ralf Baechle
2007-11-20 18:24       ` Kaz Kylheku
2007-11-20 18:24         ` Kaz Kylheku
2007-11-20 18:29       ` David Daney [this message]
2007-11-20 19:00         ` Ralf Baechle

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=4743279B.7070402@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=kaz@zeugmasystems.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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