From: Peter Zijlstra <peterz@infradead.org>
To: mingo@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org,
riel@redhat.com, mgorman@suse.de, tglx@linutronix.de,
prarit@redhat.com
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:sched/urgent] sched/numa: Fix NULL pointer dereference in task_numa_migrate()
Date: Wed, 13 Nov 2013 18:48:26 +0100 [thread overview]
Message-ID: <20131113174826.GR21461@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <tip-46a73e8a1c1720f7713b5e2df68e9dd272015b5d@git.kernel.org>
On Wed, Nov 13, 2013 at 09:25:22AM -0800, tip-bot for Rik van Riel wrote:
> + if (unlikely(!sd)) {
> + p->numa_preferred_nid = cpu_to_node(task_cpu(p));
't is only now I notice, but I added a convenience helper for this:
task_node(p) :-)
No biggie, I'll try and remember when next something near there needs
changing.
prev parent reply other threads:[~2013-11-13 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 17:25 tip-bot for Rik van Riel
2013-11-13 17:48 ` Peter Zijlstra [this message]
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=20131113174826.GR21461@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=prarit@redhat.com \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®