Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757160AbYGKTg6 (ORCPT ); Fri, 11 Jul 2008 15:36:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752078AbYGKTgv (ORCPT ); Fri, 11 Jul 2008 15:36:51 -0400 Received: from smtp-out.google.com ([216.239.33.17]:54022 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751233AbYGKTgu (ORCPT ); Fri, 11 Jul 2008 15:36:50 -0400 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=received:message-id:date:from:to:subject:cc:in-reply-to: mime-version:content-type:content-transfer-encoding: content-disposition:references; b=Hw/liQ0hr/rl6QwOMF+fRHjE0Y7VCa3Znn8Kdf+vrcJpNjs0Nf6tlRlKsXJ5hBrjn +m6uGD6V6rrUX6ge9i4rQ== Message-ID: <6599ad830807111236t2bc9aa02ned59dcc58f14b1bf@mail.gmail.com> Date: Fri, 11 Jul 2008 12:36:41 -0700 From: "Paul Menage" To: "Vegard Nossum" Subject: Re: current linux-2.6.git: cpusets completely broken Cc: "Dmitry Adamushko" , "Paul Jackson" , "Peter Zijlstra" , miaox@cn.fujitsu.com, "Linux Kernel" In-Reply-To: <19f34abd0807111207q2ad2011csdb46c6f451fe0f6d@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <19f34abd0807111207q2ad2011csdb46c6f451fe0f6d@mail.gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1122 Lines: 28 On Fri, Jul 11, 2008 at 12:07 PM, Vegard Nossum 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/