linux-kernel - Re: [patch 125/311] Cpuset hardwall flag: switch cpusets to use the bulk cgroup_add

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]

Date:	Tue, 6 May 2008 17:26:22 -0700
From:	"Paul Menage" <menage@...gle.com>
To:	"Paul Jackson" <pj@....com>
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	torvalds@...ux-foundation.org, lizf@...fujitsu.com,
	"Hidetoshi Seto" <seto.hidetoshi@...fujitsu.com>,
	"Hiroyuki KAMEZAWA" <kamezawa.hiroyu@...fujitsu.com>,
	"Dimitri Sivanich" <sivanich@....com>, linux-kernel@...r.kernel.org
Subject: Re: [patch 125/311] Cpuset hardwall flag: switch cpusets to use the bulk cgroup_add_files() API

On Tue, May 6, 2008 at 5:20 PM, Paul Jackson <pj@....com> wrote:
>
>  I definitely agree with the above observations of Paul M.  I suspect
>  that the patch might be missing the lines needed to -remove- the
>  FILE_SCHED_RELAX_DOMAIN_LEVEL cases from the old style
>  cpuset_common_file_read and cpuset_common_file_write switches.

Yes, it is - but I didn't have a tree with the relevant bits in it to
remove, as far as I could see.

>
>   2) I didn't see any replies from Paul M in response to
>     Andrews above request to "send us any needed fixup later
>     in the week".
>
>         ==> Paul M or akpm - Is this fixup in the pipeline?

Not yet - I was waiting for 2.6.26-rc1-mm1 to come out. But I can send
one against 2.6.26-rc1 directly if that helps.

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/