linux-kernel - Re: [git pull] RT scheduler updates for tip

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <496B5C2C.2050908@novell.com>
Date:	Mon, 12 Jan 2009 10:05:16 -0500
From:	Gregory Haskins <ghaskins@...ell.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Steven Rostedt <rostedt@...dmis.org>,
	Peter Zijlstra <peterz@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] RT scheduler updates for tip

Ingo Molnar wrote:
> * Gregory Haskins <ghaskins@...ell.com> wrote:
>
>   
>> Ingo Molnar wrote:
>>     
>>> * Ingo Molnar <mingo@...e.hu> wrote:
>>>
>>>   
>>>       
>>>>> Hi Ingo,
>>>>>   I have rebased the series against tip/cpus4096 as of today.  I
>>>>> built/boot this kernel for both SMP/UP on a 4-way x86_64 box, and they
>>>>> look sane.  Let me know if they still look broken to you.
>>>>>       
>>>>>           
>>> yes, i still get build failures:
>>>
>>> kernel/sched_rt.c:574: error: 'struct rq' has no member named 'cpu'
>>> kernel/sched_rt.c:619: error: 'rq' undeclared (first use in this function)
>>> kernel/sched_rt.c:619: error: (Each undeclared identifier is reported only once
>>> kernel/sched_rt.c:619: error: for each function it appears in.)
>>> kernel/sched_rt.c:667: error: 'rq' undeclared (first use in this function)
>>>
>>> so i've excluded tip/sched/rt from tip/master for now.
>>>
>>> 	Ingo
>>>   
>>>       
>> Hey Ingo,
>>   Sorry for all these problems.  I am not sure what is happening since
>> it seems to build fine for me on this end.
>>
>> I just pulled down tip/sched/rt (sha 
>> 0a6d4e1dc9154c4376358663d74060d1e33d203e) and built for my x86_64 
>> machine with both SMP and UP (configs attached).  They both completed 
>> without errors.  Could you send me the config you are having trouble 
>> with?
>>     
>
> dont have it anymore - but you can look at the build error itself and 
> figure out what config options it needs to trigger such problems 
Yes, of course.  At least one of us has engaged their brains this AM ;)

Thanks.  Fix forthcoming.

-Greg



Download attachment "signature.asc" of type "application/pgp-signature" (258 bytes)