| 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
| ||
|
Date: Mon, 3 Dec 2012 13:36:38 -0800 From: Tejun Heo <tj@...nel.org> To: Aristeu Rozanski <aris@...hat.com> Cc: linux-kernel@...r.kernel.org, Serge Hallyn <serge.hallyn@...onical.com>, cgroups@...r.kernel.org Subject: Re: [PATCH 5/5] device_cgroup: propagate local changes down the hierarchy Hello, Aristeu. On Mon, Dec 03, 2012 at 02:14:12PM -0500, Aristeu Rozanski wrote: > > Maybe I'm misunderstanding something but the behavior seems a bit > > inconsistent. So, you can't add an exception which isn't allowed by > > your parent, right? But, if your parent disallows an existing > > exception, you get to keep it? I think it would be more consistent to > > go either > > > > * Allow all settings but apply only as allowed by the parent. > > > > * Deny settings disallowed by the parent. If parent's config changes, > > delete configs which fall outside the new config. > > I prefer this one, in fact that's what was happening before and you > suggested to not remove local preferences when they're not valid > anymore. If I'm contradicting my past self, my apologies. I'm a bit conflicted about what to do myself. So, you prefer to change configurations downstream as the parent gets updated. I think you're right. Let's go with that. Thanks. -- tejun -- 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/
Powered by blists - more mailing lists