linux-kernel - Re: [PATCH] sched: Use task_rq_unlock on __sched

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1341834427.3462.42.camel@twins>
Date:	Mon, 09 Jul 2012 13:47:07 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Namhyung Kim <namhyung@...nel.org>
Cc:	Ingo Molnar <mingo@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Namhyung Kim <namhyung.kim@....com>
Subject: Re: [PATCH] sched: Use task_rq_unlock on __sched_setscheduler

On Sat, 2012-07-07 at 16:49 +0900, Namhyung Kim wrote:
> From: Namhyung Kim <namhyung.kim@....com>
> 
> It seems there's no specific reason to open-code it.  I guess the
> commit 0122ec5b02f76 ("sched: Add p->pi_lock to task_rq_lock()")
> simply missed it.  Let's be consistent with others.

Looks that way, thanks!

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