[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080910040404.245301541FE@magilla.localdomain>
Date: Tue, 9 Sep 2008 21:04:04 -0700 (PDT)
From: Roland McGrath <roland@...hat.com>
To: Oleg Nesterov <oleg@...sign.ru>
Cc: Ingo Molnar <mingo@...e.hu>, Frank Mayhar <fmayhar@...gle.com>,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Alexey Dobriyan <adobriyan@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 2.6.27-rc5] Fix itimer/many thread hang.
> As for this particular function, it seems to me that ->signal == NULL
> is not possible, no?
The concern is to make sure that the timer tick path is always safe for a
tick that hits during release_task(current) in exit_notify(). A timer tick
there can come with current->signal == NULL. We just need to make sure one
way or another that this is safe.
Thanks,
Roland
--
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