From: Pavel Machek <pavel@suse.cz>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>,
ak@suse.de, linux-kernel@vger.kernel.org, sct@redhat.com,
mingo@elte.hu
Subject: Re: 2.6.15-git7 oopses in ext3 during LTP runs
Date: Wed, 11 Jan 2006 23:40:13 +0100 [thread overview]
Message-ID: <20060111224013.GA8277@elf.ucw.cz> (raw)
In-Reply-To: <1137014875.2929.81.camel@laptopd505.fenrus.org>
On St 11-01-06 22:27:55, Arjan van de Ven wrote:
> > We expect the lock to be held on entry. Hence we expect mutex_trylock()
> > to return zero.
>
> you are correct, and the x86-64 mutex.h is buggy
>
> --- linux-2.6.15/include/asm-x86_64/mutex.h.org 2006-01-11 22:25:37.000000000 +0100
> +++ linux-2.6.15/include/asm-x86_64/mutex.h 2006-01-11 22:25:43.000000000 +0100
> @@ -104,7 +104,7 @@
> static inline int
> __mutex_fastpath_trylock(atomic_t *count, int (*fail_fn)(atomic_t *))
> {
> - if (likely(atomic_cmpxchg(count, 1, 0)) == 1)
> + if (likely(atomic_cmpxchg(count, 1, 0) == 1))
> return 1;
> else
> return 0;
>
> changes the asm to be the correct one for me.
> This is odd/evil though..
likely is the evil part here. What about this? Should make this bug
impossible to do....
Signed-off-by: Pavel Machek <pavel@suse.cz>
diff --git a/include/linux/compiler.h b/include/linux/compiler.h
--- a/include/linux/compiler.h
+++ b/include/linux/compiler.h
@@ -59,8 +59,8 @@ extern void __chk_io_ptr(void __iomem *)
* specific implementations come from the above header files
*/
-#define likely(x) __builtin_expect(!!(x), 1)
-#define unlikely(x) __builtin_expect(!!(x), 0)
+#define likely(x) (__builtin_expect(!!(x), 1))
+#define unlikely(x) (__builtin_expect(!!(x), 0))
/* Optimization barrier */
#ifndef barrier
diff --git a/kernel/sched.c b/kernel/sched.c
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -367,7 +367,7 @@ repeat_lock_task:
local_irq_save(*flags);
rq = task_rq(p);
spin_lock(&rq->lock);
- if (unlikely(rq != task_rq(p))) {
+ if unlikely(rq != task_rq(p)) {
spin_unlock_irqrestore(&rq->lock, *flags);
goto repeat_lock_task;
}
@@ -751,7 +751,7 @@ static int recalc_task_prio(task_t *p, u
else
sleep_time = (unsigned long)__sleep_time;
- if (likely(sleep_time > 0)) {
+ if likely(sleep_time > 0) {
/*
* User tasks that sleep a long time are categorised as
* idle and will get just interactive status to stay active &
@@ -876,7 +876,7 @@ static void resched_task(task_t *p)
assert_spin_locked(&task_rq(p)->lock);
- if (unlikely(test_tsk_thread_flag(p, TIF_NEED_RESCHED)))
+ if unlikely(test_tsk_thread_flag(p, TIF_NEED_RESCHED))
return;
set_tsk_thread_flag(p, TIF_NEED_RESCHED);
--
Thanks, Sharp!
next prev parent reply other threads:[~2006-01-11 22:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 20:26 2.6.15-git7 oopses in ext3 during LTP runs Andi Kleen
2006-01-11 20:46 ` Andrew Morton
2006-01-11 20:55 ` Arjan van de Ven
2006-01-11 21:07 ` Andrew Morton
2006-01-11 21:27 ` Arjan van de Ven
2006-01-11 22:19 ` Ingo Molnar
2006-01-11 22:40 ` Pavel Machek [this message]
2006-01-11 22:44 ` David S. Miller
2006-01-12 0:30 ` Ingo Molnar
2006-01-11 22:47 ` Jesper Juhl
2006-01-12 8:51 ` Pavel Machek
2006-01-12 0:55 ` 2.6.15-git7 oopses in ext3 during LTP runs II - more problems Andi Kleen
2006-01-12 1:14 ` Andrew Morton
2006-01-12 1:25 ` Andi Kleen
2006-01-11 21:25 ` 2.6.15-git7 oopses in ext3 during LTP runs Jan Engelhardt
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=20060111224013.GA8277@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sct@redhat.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