[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111229120956.GA31878@elie.Belkin>
Date: Thu, 29 Dec 2011 06:09:56 -0600
From: Jonathan Nieder <jrnieder@...il.com>
To: Greg KH <gregkh@...e.de>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
alan@...rguk.ukuu.org.uk, Thomas Gleixner <tglx@...utronix.de>,
Phil Miller <mille121@...inois.edu>
Subject: Re: [27/27] clockevents: Set noop handler in
clockevents_exchange_device()
Hi Greg,
Greg KH wrote:
> 2.6.32-longterm review patch. If anyone has any objections, please let me know.
>
> ------------------
>
> From: Thomas Gleixner <tglx@...utronix.de>
>
> commit de28f25e8244c7353abed8de0c7792f5f883588c upstream.
[...]
> --- a/kernel/time/clockevents.c
> +++ b/kernel/time/clockevents.c
> @@ -221,6 +221,7 @@ void clockevents_exchange_device(struct
> * released list and do a notify add later.
> */
> if (old) {
> + old->event_handler = clockevents_handle_noop;
> clockevents_set_mode(old, CLOCK_EVT_MODE_UNUSED);
This is basically the reverse of 7c1e768974 (clockevents: prevent
clockevent event_handler ending up handler_noop, 2008-09-03). The
rationale for the latter still applies. People have been reporting
the analagous patch to this one causing hangs on resume in 3.1.y and
3.2 release candidates:
- http://thread.gmane.org/gmane.linux.kernel/1233033
- http://thread.gmane.org/gmane.linux.kernel/1233389
- http://thread.gmane.org/gmane.linux.kernel/1233159
- http://thread.gmane.org/gmane.linux.kernel/1227868/focus=1230877
So please consider reverting it for now.
Thanks,
Jonathan
--
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