[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130215153059.8ac35241.akpm@linux-foundation.org>
Date: Fri, 15 Feb 2013 15:30:59 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Mandeep Singh Baines <msb@...omium.org>
Cc: linux-kernel@...r.kernel.org, Oleg Nesterov <oleg@...hat.com>,
Tejun Heo <tj@...nel.org>, "Rafael J. Wysocki" <rjw@...k.pl>,
Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH 3/5] coredump: cleanup the waiting for coredump_finish
code
On Thu, 14 Feb 2013 15:38:14 -0800
Mandeep Singh Baines <msb@...omium.org> wrote:
> Replace the for loop with a simple if.
Well OK, but why? Presumably the loop was added for a reason and
presumably you believe that reason to be (no longer?) correct. Please
describe all these things.
> --- a/kernel/exit.c
> +++ b/kernel/exit.c
> @@ -479,12 +479,9 @@ static void exit_mm(struct task_struct * tsk)
> if (atomic_dec_and_test(&core_state->nr_threads))
> complete(&core_state->startup);
>
> - for (;;) {
> - set_task_state(tsk, TASK_UNINTERRUPTIBLE);
> - if (!self.task) /* see coredump_finish() */
> - break;
> + set_task_state(tsk, TASK_UNINTERRUPTIBLE);
> + if (self.task) /* see coredump_finish() */
> schedule();
> - }
--
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