linux-kernel - Re: current linux-2.6.git: cpusets completely broken

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: <6599ad830807111236t2bc9aa02ned59dcc58f14b1bf@mail.gmail.com>
Date:	Fri, 11 Jul 2008 12:36:41 -0700
From:	"Paul Menage" <menage@...gle.com>
To:	"Vegard Nossum" <vegard.nossum@...il.com>
Cc:	"Dmitry Adamushko" <dmitry.adamushko@...il.com>,
	"Paul Jackson" <pj@....com>,
	"Peter Zijlstra" <a.p.zijlstra@...llo.nl>, miaox@...fujitsu.com,
	"Linux Kernel" <linux-kernel@...r.kernel.org>
Subject: Re: current linux-2.6.git: cpusets completely broken

On Fri, Jul 11, 2008 at 12:07 PM, Vegard Nossum <vegard.nossum@...il.com> wrote:
>
> The result of having CPUSETS enabled as above is a 100% reproducible
> BUG on the very first cpu hot-unplug:
>
> ------------[ cut here ]------------
> kernel BUG at xxx/linux-2.6/kernel/sched.c:5859!

That doesn't quite match up with any BUG in 2.6.26-rc9 - what tree is
this last crash based on?

>
> Also, this is on the latest linux-2.6.git! Since we're so close to
> release, maybe cpusets should simply be marked BROKEN for now? (Unless
> we can fix it, of course. The alternative is to apply Miao Xie's
> workaround patch temporarily.)

If we were going to mark anything as broken, wouldn't cpu-hotplug be
the more appropriate victim? I suspect that there are more systems
using cpusets in production environments than using cpu hotplug. But
as you say, fixing it sounds better.

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