From: Jarek Poplawski <jarkao2@o2.pl>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [patch] lockdep: fix possible races while disabling lock-debugging
Date: Fri, 8 Dec 2006 07:27:26 +0100 [thread overview]
Message-ID: <20061208062725.GA1012@ff.dom.local> (raw)
In-Reply-To: <20061207132903.GA341@elte.hu>
On Thu, Dec 07, 2006 at 02:29:03PM +0100, Ingo Molnar wrote:
> Subject: [patch] lockdep: fix possible races while disabling lock-debugging
> From: Ingo Molnar <mingo@elte.hu>
...
> (also note that as we all know the Linux kernel is, by definition,
> bug-free and perfect, so this code never triggers, so these fixes are
> highly theoretical. I wrote this patch for aesthetic reasons alone.)
Now it's too sexy! I can't work.
PS: I had some problems with patching - probably
because of something from -mm, but:
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
...
> @@ -567,12 +601,10 @@ static noinline int print_circular_bug_t
> if (debug_locks_silent)
> return 0;
>
> - /* hash_lock unlocked by the header */
> - __raw_spin_lock(&hash_lock);
> this.class = check_source->class;
> if (!save_trace(&this.trace))
> return 0;
> - __raw_spin_unlock(&hash_lock);
> +
IMHO lock is needed here for save_trace.
...
> @@ -1212,7 +1244,8 @@ register_lock_class(struct lockdep_map *
> hash_head = classhashentry(key);
>
> raw_local_irq_save(flags);
> - __raw_spin_lock(&hash_lock);
> + if (!graph_lock())
! raw_local_irq_restore(flags);
> + return NULL;
> /*
> * We have to do the hash-walk again, to avoid races
> * with another CPU:
Jarek P.
next prev parent reply other threads:[~2006-12-08 6:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 13:29 [patch] lockdep: fix possible races while disabling lock-debugging Ingo Molnar
2006-12-08 6:27 ` Jarek Poplawski [this message]
2006-12-11 7:23 ` Ingo Molnar
2006-12-11 7:28 ` [patch] lockdep: fix possible race while disabling lock-debugging, restore fix Ingo Molnar
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=20061208062725.GA1012@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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