All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: gavin.guo@canonical.com, linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, jay.vosburgh@canonical.com,
	liang.chen@canonical.com, mgorman@suse.de, mingo@redhat.com,
	peterz@infradead.org
Subject: Re: [PATCH] sched/numa: Fix use-after-free bug in the task_numa_compare
Date: Mon, 18 Jan 2016 09:03:19 -0500	[thread overview]
Message-ID: <569CF0A7.4000306@redhat.com> (raw)
In-Reply-To: <1453125548-2762-1-git-send-email-gavin.guo@canonical.com>

On 01/18/2016 08:59 AM, gavin.guo@canonical.com wrote:
> From: Gavin Guo <gavin.guo@canonical.com>

> As commit 1effd9f19324 ("sched/numa: Fix unsafe get_task_struct() in
> task_numa_assign()") points out, the rcu_read_lock() cannot protect the
> task_struct from being freed in the finish_task_switch(). And the bug
> happens in the process of calculation of imp which requires the access of
> p->numa_faults being freed in the following path:
> 
> do_exit()
>         current->flags |= PF_EXITING;
>     release_task()
>         ~~delayed_put_task_struct()~~
>     schedule()
>     ...
>     ...
> rq->curr = next;
>     context_switch()
>         finish_task_switch()
>             put_task_struct()
>                 __put_task_struct()
> 		    task_numa_free()
> 
> The fix here to get_task_struct() early before end of dst_rq->lock to
> protect the calculation process and also put_task_struct() in the
> corresponding point if finally the dst_rq->curr somehow cannot be
> assigned.
> 
> BugLink: https://bugs.launchpad.net/bugs/1527643
> Signed-off-by: Gavin Guo <gavin.guo@canonical.com>
> Signed-off-by: Liang Chen <liangchen.linux@gmail.com>

Reviewed-by: Rik van Riel <riel@redhat.com>

-- 
All rights reversed

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Rik van Riel <riel@redhat.com>
To: gavin.guo@canonical.com, linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, jay.vosburgh@canonical.com,
	liang.chen@canonical.com, mgorman@suse.de, mingo@redhat.com,
	peterz@infradead.org
Subject: Re: [PATCH] sched/numa: Fix use-after-free bug in the task_numa_compare
Date: Mon, 18 Jan 2016 09:03:19 -0500	[thread overview]
Message-ID: <569CF0A7.4000306@redhat.com> (raw)
In-Reply-To: <1453125548-2762-1-git-send-email-gavin.guo@canonical.com>

On 01/18/2016 08:59 AM, gavin.guo@canonical.com wrote:
> From: Gavin Guo <gavin.guo@canonical.com>

> As commit 1effd9f19324 ("sched/numa: Fix unsafe get_task_struct() in
> task_numa_assign()") points out, the rcu_read_lock() cannot protect the
> task_struct from being freed in the finish_task_switch(). And the bug
> happens in the process of calculation of imp which requires the access of
> p->numa_faults being freed in the following path:
> 
> do_exit()
>         current->flags |= PF_EXITING;
>     release_task()
>         ~~delayed_put_task_struct()~~
>     schedule()
>     ...
>     ...
> rq->curr = next;
>     context_switch()
>         finish_task_switch()
>             put_task_struct()
>                 __put_task_struct()
> 		    task_numa_free()
> 
> The fix here to get_task_struct() early before end of dst_rq->lock to
> protect the calculation process and also put_task_struct() in the
> corresponding point if finally the dst_rq->curr somehow cannot be
> assigned.
> 
> BugLink: https://bugs.launchpad.net/bugs/1527643
> Signed-off-by: Gavin Guo <gavin.guo@canonical.com>
> Signed-off-by: Liang Chen <liangchen.linux@gmail.com>

Reviewed-by: Rik van Riel <riel@redhat.com>

-- 
All rights reversed

  reply	other threads:[~2016-01-18 14:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 13:59 [PATCH] sched/numa: Fix use-after-free bug in the task_numa_compare gavin.guo
2016-01-18 13:59 ` gavin.guo
2016-01-18 14:03 ` Rik van Riel [this message]
2016-01-18 14:03   ` Rik van Riel
2016-01-18 14:33 ` Peter Zijlstra
2016-01-18 14:33   ` Peter Zijlstra
2016-01-18 15:24   ` [PATCH V2] " gavin.guo
2016-01-18 15:24     ` gavin.guo
2016-01-18 17:13     ` Peter Zijlstra
2016-01-18 17:13       ` Peter Zijlstra
2016-01-18 23:40       ` Gavin Guo
2016-01-18 23:40         ` Gavin Guo
2016-01-19  9:35         ` Ingo Molnar
2016-01-19  9:35           ` Ingo Molnar
2016-01-20  4:36           ` [PATCH V3] " gavin.guo
2016-01-20  4:36             ` gavin.guo
2016-01-21 18:55             ` [tip:sched/urgent] " tip-bot for Gavin Guo
2016-01-22 12:55             ` tip-bot for Gavin Guo

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=569CF0A7.4000306@redhat.com \
    --to=riel@redhat.com \
    --cc=gavin.guo@canonical.com \
    --cc=jay.vosburgh@canonical.com \
    --cc=liang.chen@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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 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.