public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: akpm@linux-foundation.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	jk@ozlabs.org, mingo@elte.hu
Subject: Re: + mutex-debug-check-mutex-magic-before-owner.patch added to -mm tree
Date: Sun, 27 Apr 2008 22:54:37 +0200	[thread overview]
Message-ID: <1209329677.6429.0.camel@lappy> (raw)
In-Reply-To: <200804272047.m3RKlMgY024122@imap1.linux-foundation.org>

On Sun, 2008-04-27 at 13:47 -0700, akpm@linux-foundation.org wrote:
> The patch titled
>      mutex-debug: check mutex magic before owner
> has been added to the -mm tree.  Its filename is
>      mutex-debug-check-mutex-magic-before-owner.patch
> 
> Before you just go and hit "reply", please:
>    a) Consider who else should be cc'ed
>    b) Prefer to cc a suitable mailing list as well
>    c) Ideally: find the original patch on the mailing list and do a
>       reply-to-all to that, adding suitable additional cc's
> 
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
> 
> See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
> out what to do about this
> 
> The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
> 
> ------------------------------------------------------
> Subject: mutex-debug: check mutex magic before owner
> From: Jeremy Kerr <jk@ozlabs.org>
> 
> Currently, the mutex debug code checks the lock->owner before lock->magic, so
> a corrupt mutex will most likely result in failing the owner check, rather
> than the magic check.
> 
> This change to debug_mutex_unlock does the magic check first, so
> we have a better idea of what breaks.
> 
> Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>

Acked-by; Peter Zijlstra <a.p.zijlstra@chello.nl>

> Cc: Ingo Molnar <mingo@elte.hu>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
> 
>  kernel/mutex-debug.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff -puN kernel/mutex-debug.c~mutex-debug-check-mutex-magic-before-owner kernel/mutex-debug.c
> --- a/kernel/mutex-debug.c~mutex-debug-check-mutex-magic-before-owner
> +++ a/kernel/mutex-debug.c
> @@ -79,8 +79,8 @@ void debug_mutex_unlock(struct mutex *lo
>  	if (unlikely(!debug_locks))
>  		return;
>  
> -	DEBUG_LOCKS_WARN_ON(lock->owner != current_thread_info());
>  	DEBUG_LOCKS_WARN_ON(lock->magic != lock);
> +	DEBUG_LOCKS_WARN_ON(lock->owner != current_thread_info());
>  	DEBUG_LOCKS_WARN_ON(!lock->wait_list.prev && !lock->wait_list.next);
>  	DEBUG_LOCKS_WARN_ON(lock->owner != current_thread_info());
>  }
> _
> 
> Patches currently in -mm which might be from jk@ozlabs.org are
> 
> origin.patch
> mutex-debug-check-mutex-magic-before-owner.patch
> 


           reply	other threads:[~2008-04-27 20:55 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200804272047.m3RKlMgY024122@imap1.linux-foundation.org>]

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=1209329677.6429.0.camel@lappy \
    --to=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=jk@ozlabs.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