linux-kernel - Re: [PATCH v3 3/3] sched: Rework check_for

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]

Date:	Thu, 26 Jun 2014 17:00:42 +0530
From:	Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
To:	Kirill Tkhai <ktkhai@...allels.com>
Cc:	linux-kernel@...r.kernel.org,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...nel.org>, tkhai@...dex.ru,
	Mike Galbraith <umgwanakikbuti@...il.com>,
	khorenko@...allels.com, Ben Segall <bsegall@...gle.com>,
	Paul Turner <pjt@...gle.com>
Subject: Re: [PATCH v3 3/3] sched: Rework check_for_tasks()

* Kirill Tkhai <ktkhai@...allels.com> [2014-06-25 12:19:55]:

> 
> 1)Iterate thru all of threads in the system.
>   Check for all threads, not only for group leaders.
> 
> 2)Check for p->on_rq instead of p->state and cputime.
>   Preempted task in !TASK_RUNNING state  OR just
>   created task may be queued, that we want to be
>   reported too.
> 
> 3)Use read_lock() instead of write_lock().
>   This function does not change any structures, and
>   read_lock() is enough.
> 
> Signed-off-by: Kirill Tkhai <ktkhai@...allels.com>
> CC: Konstantin Khorenko <khorenko@...allels.com>
> CC: Ben Segall <bsegall@...gle.com>
> CC: Paul Turner <pjt@...gle.com>
> CC: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
> CC: Mike Galbraith <umgwanakikbuti@...il.com>
> CC: Peter Zijlstra <peterz@...radead.org>
> CC: Ingo Molnar <mingo@...nel.org>
> ---
 
Reviewed-by: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>

-- 
Thanks and Regards
Srikar Dronamraju

--
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/