linux-kernel - Re: [PATCH] sched: fix env->src

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: <CAKfTPtAA_k6C_1YMjm2ZxU_Y4VgEk6QOwee9ShbD3Jw8GwY1eg@mail.gmail.com>
Date:	Thu, 14 Feb 2013 09:32:35 +0100
From:	Vincent Guittot <vincent.guittot@...aro.org>
To:	Damien Wyart <damien.wyart@...il.com>
Cc:	linux-kernel@...r.kernel.org, linaro-dev@...ts.linaro.org,
	peterz@...radead.org, mingo@...nel.org,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH] sched: fix env->src_cpu for active migration

On 13 February 2013 21:02, Damien Wyart <damien.wyart@...il.com> wrote:
>> Bingo, that was the problem in my setup: as the patch was applied
>> through a script with others, I had missed the error message about the
>> conflict (I have also another conflict which can be safely ignored so
>> the new one did not catch my eye)... So the patch was only
>> half-applied, and the final code is broken.
>
>> How did you solve the conflict (I am not a scheduler expert)? I can
>> retry running the patched kernel with your resolution, to check if
>> everything is ok.
>
> After looking a bit more, the conflict resolution seemed straighforward,

Yes the resolution is straightforward and your patch is ok.

> so I gave it a go. The attached version booted fine, so the initial
> problem was purely PEBCAK... Sorry for the noise!

Now, i know that my patch on frederic's branch, boots on a x86_64,
Core i7 920 :-)

Vincent

>
> --
> Damien
--
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/