[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 9 Sep 2013 22:22:23 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: maarten.lankhorst@...onical.com
Cc: imirkin@...m.mit.edu, linux-kernel@...r.kernel.org,
daniel.vetter@...ll.ch, robdclark@...il.com,
a.p.zijlstra@...llo.nl, mingo@...nel.org
Subject: Re: [3.11-rc1] CONFIG_DEBUG_MUTEXES=y using gcc 3.x makes unbootablekernel.
Maarten Lankhorst wrote:
> Yeah looks ok, did you run the selftests from CONFIG_DEBUG_LOCKING_API_SELFTESTS,
> with/without CONFIG_PROVE_LOCKING and once more with DEBUG_MUTEXES also unset?
Since CONFIG_DEBUG_MUTEXES=n && CONFIG_PROVE_LOCKING=y is impossible, I tested
CONFIG_DEBUG_MUTEXES=y
CONFIG_PROVE_LOCKING=y
CONFIG_DEBUG_LOCKING_API_SELFTESTS=y
CONFIG_DEBUG_MUTEXES=y
CONFIG_PROVE_LOCKING=n
CONFIG_DEBUG_LOCKING_API_SELFTESTS=y
CONFIG_DEBUG_MUTEXES=n
CONFIG_PROVE_LOCKING=n
CONFIG_DEBUG_LOCKING_API_SELFTESTS=y
CONFIG_DEBUG_MUTEXES=y
CONFIG_PROVE_LOCKING=y
CONFIG_DEBUG_LOCKING_API_SELFTESTS=n
CONFIG_DEBUG_MUTEXES=y
CONFIG_PROVE_LOCKING=n
CONFIG_DEBUG_LOCKING_API_SELFTESTS=n
CONFIG_DEBUG_MUTEXES=n
CONFIG_PROVE_LOCKING=n
CONFIG_DEBUG_LOCKING_API_SELFTESTS=n
and all works OK.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists