linux-kernel - Re: [PATCH] task containersv11 enable containers by default in some configs

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]

Message-ID: <6599ad830709171108n2927d1fegcf05d564d4be0f6f@mail.gmail.com>
Date:	Mon, 17 Sep 2007 11:08:03 -0700
From:	"Paul Menage" <menage@...gle.com>
To:	"Paul Jackson" <pj@....com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] task containersv11 enable containers by default in some configs

On 9/15/07, Paul Jackson <pj@....com> wrote:
> From: Paul Jackson <pj@....com>
>
> Paul Menage - in pre-container cpusets, a few config files enabled
> cpusets by default.  Could you blend the following patch into your
> container patch set, so that cpusets continue to be configured by
> default for those same configurations?
>

OK, I'll take care of that.

After talking with akpm, it sounds as though some of the nasty aspects
of "select" in Kconfig rules can be avoided as long as no config
option is controlled by both "select" and "depends". So I'll probably
go back to making things like CONFIG_CPUSETS select CONFIG_CGROUPS,
and enforce that CONFIG_CGROUPS can't depend on anything.

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/