lkml.org 
[lkml]   [2008]   [Mar]   [10]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateMon, 10 Mar 2008 10:13:21 +0100
FromIngo Molnar <>
SubjectRe: [PATCH] Fix check after use in kernel/exit.c
* WANG Cong <xiyou.wangcong@gmail.com> wrote:

> --- a/kernel/exit.c
> +++ b/kernel/exit.c
> @@ -583,8 +583,6 @@ static void exit_mm(struct task_struct * tsk)
>  	struct mm_struct *mm = tsk->mm;
> 
>  	mm_release(tsk, mm);
> -	if (!mm)
> -		return;

> @@ -464,6 +464,8 @@ void mm_release(struct task_struct *tsk, struct mm_struct *mm)
>  {
>  	struct completion *vfork_done = tsk->vfork_done;
> 
> +	if (!mm)
> +		return;
>  	/* Get rid of any cached register state */
>  	deactivate_mm(tsk, mm);

no, this is buggy in the same way - we wont do a deactivate_mm() for 
kernel threads. The check should be left alone in exit_mm(), we should 
at most add a check for NULL mm to this place:

        if (tsk->clear_child_tid
            && !(tsk->flags & PF_SIGNALED)
            && atomic_read(&mm->mm_users) > 1) {
but ... can mm in fact ever be NULL if tsk->clear_child_tid is set?

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2008-03-10 10:17    [from the cache]
©2003-2008