From: Ingo Molnar <mingo@elte.hu>
To: Brice Goglin <Brice.Goglin@ens-lyon.org>
Cc: Andrew Morton <akpm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.15-mm4
Date: Sun, 15 Jan 2006 05:42:05 +0100 [thread overview]
Message-ID: <20060115044205.GA7456@elte.hu> (raw)
In-Reply-To: <43C9CE62.9070302@ens-lyon.org>
* Brice Goglin <Brice.Goglin@ens-lyon.org> wrote:
> >Could you try the patch below?
>
> Yes, it does fix it. What's the bug ? The mutexes are supposed to work
> where semaphores do, aren't they ?
no, not always. We could introduce mutex_trylock_irqsafe() and
mutex_unlock_irqsafe(), but it's probably not worth doing it - it's just
3-4 cases so far, out of hundreds of mutex conversions.
Ingo
next prev parent reply other threads:[~2006-01-15 4:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 15:34 2.6.15-mm4 Brice Goglin
2006-01-15 4:07 ` 2.6.15-mm4 Ingo Molnar
2006-01-15 4:24 ` 2.6.15-mm4 Brice Goglin
2006-01-15 4:42 ` Ingo Molnar [this message]
[not found] <20060114055153.04684592.akpm@osdl.org>
2006-01-14 22:49 ` 2.6.15-mm4 Reuben Farrelly
2006-01-16 4:08 ` 2.6.15-mm4 Tejun Heo
2006-01-14 23:10 ` 2.6.15-mm4 Reuben Farrelly
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=20060115044205.GA7456@elte.hu \
--to=mingo@elte.hu \
--cc=Brice.Goglin@ens-lyon.org \
--cc=akpm@osdl.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