From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Salman Qazi <sqazi@google.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched: fix fork() error path to not crash.
Date: Tue, 26 Jun 2012 10:40:08 +0200 [thread overview]
Message-ID: <1340700008.21991.35.camel@twins> (raw)
In-Reply-To: <20120626011815.11323.5533.stgit@dungbeetle.mtv.corp.google.com>
On Mon, 2012-06-25 at 18:18 -0700, Salman Qazi wrote:
> In dup_task_struct, if arch_dup_task_struct fails, the clean up
> code fails to clean up correctly. That's because the clean up
> code depends on unininitalized ti->task pointer. We fix this
> by making sure that the task and thread_info know about each other
> before we attempt to take the error path.
>
> Signed-off-by: Salman Qazi <sqazi@google.com>
Cute, however did you find that?
next prev parent reply other threads:[~2012-06-26 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 1:18 [PATCH] sched: fix fork() error path to not crash Salman Qazi
2012-06-26 8:40 ` Peter Zijlstra [this message]
2012-06-26 16:58 ` Salman Qazi
2012-07-06 6:18 ` [tip:sched/core] sched: Fix " tip-bot for Salman Qazi
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=1340700008.21991.35.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=sqazi@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox