All of lore.kernel.org
 help / color / mirror / Atom feed
From: Preeti U Murthy <preeti@linux.vnet.ibm.com>
To: Guenter Roeck <linux@roeck-us.net>,
	stable <stable@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Ingo Molnar <mingo@kernel.org>
Subject: Re: 4.0.2-stable-queue build failures due to 'clockevents: Fix cpu_down() race for hrtimer based broadcasting'
Date: Mon, 11 May 2015 11:20:17 +0530	[thread overview]
Message-ID: <55504319.9090501@linux.vnet.ibm.com> (raw)
In-Reply-To: <554FFEED.6030308@roeck-us.net>

On 05/11/2015 06:29 AM, Guenter Roeck wrote:
> Build is still going on, so there may be other affected architectures.
> 
> ---
> 
> Building ia64:defconfig ... failed
> Building parisc:generic-32bit_defconfig ... failed
> --------------
> Error log:
> kernel/cpu.c: In function '_cpu_down':
> kernel/cpu.c:415:2: error: implicit declaration of function
> 'hotplug_cpu__broadcast_tick_pull' [-Werror=implicit-function-declaration]
> cc1: some warnings being treated as errors
> 
> ---
> 
> Bisect log:
> 
> # bad: [c71309a3658d323d56261d4590b2c5214e61b05f] clockevents: Fix
> cpu_down() race for hrtimer based broadcasting
> # good: [072cab659c9368586d6417cfd6ec2d2c68469c67] Linux 4.0.2
> git bisect start 'HEAD' 'v4.0.2'
> # good: [7e62c9a30d01ac14be2bc3e048b737e1b0c8d08d] cdc-acm: prevent
> infinite loop when parsing CDC headers.
> git bisect good 7e62c9a30d01ac14be2bc3e048b737e1b0c8d08d
> # good: [8b55f847f1e9964ac2ab657cc0e1334ed8be214c] ext4: fix data
> corruption caused by unwritten and delayed extents
> git bisect good 8b55f847f1e9964ac2ab657cc0e1334ed8be214c
> # good: [7c0e04a5e08bec7f9101d20214f92b5f466a556b] drm/radeon: only mark
> audio as connected if the monitor supports it (v3)
> git bisect good 7c0e04a5e08bec7f9101d20214f92b5f466a556b
> # good: [da9778d808f0629fd804421e97294f25b81b1885] drm/radeon: fix
> lockup when BOs aren't part of the VM on release
> git bisect good da9778d808f0629fd804421e97294f25b81b1885
> # good: [68cd28ab24ce16ac7f3978a7627eae5b599c3d8b] drm/radeon: check new
> address before removing old one
> git bisect good 68cd28ab24ce16ac7f3978a7627eae5b599c3d8b
> # good: [c20b6545f649724a733e008e7124fa9d1e114c71] Drivers: hv: vmbus:
> Don't wait after requesting offers
> git bisect good c20b6545f649724a733e008e7124fa9d1e114c71
> # first bad commit: [c71309a3658d323d56261d4590b2c5214e61b05f]
> clockevents: Fix cpu_down() race for hrtimer based broadcasting
> 
> ---
> 
> Reverting the bad commit fixes the problem.

Please let me know if the following patch fixes the issue:

    clockevents: Fix build error caused by fix for hotplug race with hrtimer broadcast
    
    commit: c71309a3658d ("clockevents: Fix cpu_down() race for hrtimer based broadcasting")
    causes a build error on certain archs where CONFIG_GENERIC_CLOCKEVENTS
    is not set. This patch fixes this.
    
    Signed-off-by: Preeti U. Murthy <preeti@linux.vnet.ibm.com>

diff --git a/include/linux/tick.h b/include/linux/tick.h
index e3e9d20..b62ff06 100644
--- a/include/linux/tick.h
+++ b/include/linux/tick.h
@@ -134,6 +134,7 @@ static inline void tick_clock_notify(void) { }
 static inline int tick_check_oneshot_change(int allow_nohz) { return 0; }
 static inline void tick_irq_enter(void) { }
 static inline int tick_oneshot_mode_active(void) { return 0; }
+static inline void hotplug_cpu__broadcast_tick_pull(int dead_cpu) { }
 #endif /* !CONFIG_GENERIC_CLOCKEVENTS */
 
 # ifdef CONFIG_NO_HZ_COMMON


Thanks

Regards
Preeti U Murthy
> 
> Guenter
> 


  reply	other threads:[~2015-05-11  5:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11  0:59 4.0.2-stable-queue build failures due to 'clockevents: Fix cpu_down() race for hrtimer based broadcasting' Guenter Roeck
2015-05-11  5:50 ` Preeti U Murthy [this message]
2015-05-11 12:18   ` Greg Kroah-Hartman
2015-05-11 13:02   ` Guenter Roeck
2015-05-12  6:07     ` Preeti U Murthy
2015-05-12 12:14       ` Greg Kroah-Hartman
2015-05-12 23:55         ` Preeti U Murthy
2015-05-11 12:18 ` Greg Kroah-Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55504319.9090501@linux.vnet.ibm.com \
    --to=preeti@linux.vnet.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux@roeck-us.net \
    --cc=mingo@kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.