[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150911102438.GA7579@linux.vnet.ibm.com>
Date: Fri, 11 Sep 2015 15:54:38 +0530
From: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
To: Oleg Nesterov <oleg@...hat.com>
Cc: Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Kirill Tkhai <ktkhai@...allels.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] check_for_tasks: read_lock(tasklist_lock) doesn't need
to disable irqs
* Oleg Nesterov <oleg@...hat.com> [2015-09-10 15:07:50]:
> check_for_tasks() doesn't need to disable irqs, recursive read_lock()
> from interrupt is fine.
>
> While at it, s/do_each_thread/for_each_process_thread/.
>
> Signed-off-by: Oleg Nesterov <oleg@...hat.com>
Looks good to me.
Reviewed-by: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
> ---
> kernel/cpu.c | 8 ++++----
> 1 files changed, 4 insertions(+), 4 deletions(-)
>
--
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/
Powered by blists - more mailing lists