All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Nick Piggin <npiggin@suse.de>,
	Vegard Nossum <vegard.nossum@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: lockdep and debug objects together are broken?
Date: Wed, 21 Jan 2009 12:54:51 +0100	[thread overview]
Message-ID: <20090121115451.GA20696@elte.hu> (raw)
In-Reply-To: <1232538602.4847.158.camel@laptop>


* Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:

> On Wed, 2009-01-21 at 12:42 +0100, Ingo Molnar wrote:
> 
> > So by the time you'd rearm, there's a lot of tasks with no proper 
> > locking state built up. We might be able to re-arm via 
> > stop_machine_run perhaps.
> 
> Won't work either, kstopmachine only preempts everybody. We'd require 
> something stronger.

indeed - mutexes wont be covered.

> What we need is a point where there's guaranteed no locks held, for 
> regular tasks that would be a trip to userspace and back, but for kernel 
> tasks that's a bit harder -- does the freezer stuff guarantee this?

yes, that might be doable.

Sounds very fragile though.

	Ingo

  reply	other threads:[~2009-01-21 11:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20  8:55 lockdep and debug objects together are broken? Nick Piggin
2009-01-20 21:11 ` Vegard Nossum
2009-01-21  7:19   ` Nick Piggin
2009-01-21 11:42     ` Ingo Molnar
2009-01-21 11:50       ` Peter Zijlstra
2009-01-21 11:54         ` Ingo Molnar [this message]
2009-01-21 11:54       ` Nick Piggin
2009-01-21 11:57         ` 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=20090121115451.GA20696@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --cc=tglx@linutronix.de \
    --cc=vegard.nossum@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.