linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Guillaume Autran <gautran@mrv.com>
To: Eugene Surovegin <ebs@ebshome.net>
Cc: akpm@osdl.org, linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] ppc32: fix destroy_context() race condition
Date: Tue, 12 Jul 2005 14:29:04 -0400	[thread overview]
Message-ID: <42D40BF0.6040605@mrv.com> (raw)
In-Reply-To: <20050712163921.GE25918@gate.ebshome.net>

[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]

Eugene, destroy_context(..) can be called from other place outside of 
the scheduler and switch_mm(...). See mmdrop(...) for example.
In many of those cases, the task will run with preemption enable.

Guillaume.


Eugene Surovegin wrote:

>On Tue, Jul 12, 2005 at 10:23:51AM -0400, Guillaume Autran wrote:
>  
>
>>Fix for a race condition when a task gets preempted by another task
>>while executing the destroy_context(...) in a FEW_CONTEXTS environment.
>>mm->context == NO_CONTEXT but the context_map may indicate all contexts
>>are in use.
>>The solution to this problem is to disable kernel preemption while
>>destroying a MMU context.
>>
>>Signed-off-by: Guillaume Autran <gautran@mrv.com>
>>
>>---
>>
>>diff -Nru a/include/asm-ppc/mmu_context.h b/include/asm-ppc/mmu_context.h
>>--- a/include/asm-ppc/mmu_context.h	2005-06-17 15:48:29.000000000 -0400
>>+++ b/include/asm-ppc/mmu_context.h	2005-07-05 08:58:46.000000000 -0400
>>@@ -149,6 +149,7 @@
>>*/
>>static inline void destroy_context(struct mm_struct *mm)
>>{
>>+	preempt_disable();
>>	if (mm->context != NO_CONTEXT) {
>>		clear_bit(mm->context, context_map);
>>		mm->context = NO_CONTEXT;
>>@@ -156,6 +157,7 @@
>>		atomic_inc(&nr_free_contexts);
>>#endif
>>	}
>>+	preempt_enable();
>>}
>>
>>static inline void switch_mm(struct mm_struct *prev, struct mm_struct *next,
>>
>>    
>>
>
>Could you explain, why this patch is needed?
>
>AFAIK, destroy_context() is only called from switch_mm(), which in 
>turn is called from schedule() with preemption already disabled. If 
>not, IMHO we have bigger problems, and "fixing" destroy_context() will 
>only hide such problems.
>
>  
>

-- 
=======================================
Guillaume Autran
Senior Software Engineer
MRV Communications, Inc.
Tel: (978) 952-4932 office
E-mail: gautran@mrv.com
======================================= 


[-- Attachment #2: Type: text/html, Size: 2432 bytes --]

  reply	other threads:[~2005-07-12 18:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12 14:23 [PATCH] ppc32: fix destroy_context() race condition Guillaume Autran
2005-07-12 16:39 ` Eugene Surovegin
2005-07-12 18:29   ` Guillaume Autran [this message]
2005-07-12 18:45     ` Eugene Surovegin
2005-07-13  0:09 ` Benjamin Herrenschmidt

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=42D40BF0.6040605@mrv.com \
    --to=gautran@mrv.com \
    --cc=akpm@osdl.org \
    --cc=ebs@ebshome.net \
    --cc=linuxppc-embedded@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).