lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Sun, 22 Jul 2012 20:45:00 +0200
From:	Alexandre Ferrando <alferpal@...il.com>
To:	Thomas Backlund <tmb@...eia.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: Build fails in 3.4.6

On 22 July 2012 20:01, Thomas Backlund <tmb@...eia.org> wrote:
> 22.07.2012 18:02, Alexandre Ferrando skrev:
>> Summary: Linux kernel 3.4.6 fails to build in some cases when
>> CONFIG_NO_HZ is set
>>
>> Full description: Kernel build using configurations [ 0 ] (mine,
>> trying to build the zen kernel) and [ 1 ] (from someone using
>> slackware) fail to build with this error message when CONFIG_NO_HZ is
>> set:
>>
>> kernel/built-in.o: In function `tick_nohz_stop_sched_tick.isra.9':
>> tick-sched.c:(.text+0x4a3e9): undefined reference to `calc_load_enter_idle'
>> kernel/built-in.o: In function `tick_nohz_idle_exit':
>> (.text+0x4a767): undefined reference to `calc_load_exit_idle'
>>
>> Unsetting CONFIG_NO_HZ solves the issue.
>>
>> However, CONFIG_NO_HZ seems not to be the root of the problem because
>> this configuration [ 2 ] of the zen kernel and Arch's stock kernel [ 3
>> ] both build with CONFIG_NO_HZ set
>
> This fallout comes from the BFS scheduler patch in zen kernel that is
> not updated/adapted for the:
>
> sched-nohz-rewrite-and-fix-load-avg-computation-again.patch
>
> that went into 3.4.6
>
>
> --
> Thomas
>
>

Thank you for pointing out the root of the issue.

I apologize for bringing in an issue related to code not included into
the mainstream kernel.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ