From mboxrd@z Thu Jan 1 00:00:00 1970 From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman) Subject: Re: [CFT][PATCH 09/10] sysfs: Create mountpoints with sysfs_create_empty_dir Date: Tue, 11 Aug 2015 23:04:28 -0500 Message-ID: <871tf9b19v.fsf@x220.int.ebiederm.org> References: <87pp63jcca.fsf@x220.int.ebiederm.org> <878ucrhxi9.fsf@x220.int.ebiederm.org> <20150811184426.GH23408@mtj.duckdns.org> <877fp1hcuj.fsf@x220.int.ebiederm.org> <87fv3pe3zn.fsf@x220.int.ebiederm.org> <87a8txb1k8.fsf@x220.int.ebiederm.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <87a8txb1k8.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org> (Eric W. Biederman's message of "Tue, 11 Aug 2015 22:58:15 -0500") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Tejun Heo Cc: Linux API , Linux Containers , Greg Kroah-Hartman , Andy Lutomirski , Kenton Varda , Michael Kerrisk-manpages , Richard Weinberger , LINUXFS-ML List-Id: containers.vger.kernel.org ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman) writes: > ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman) writes: > >> I just went and attempted to reproduce this, and on RHEL6 workstation >> (aka my work laptop), using the todays 4.2.0-rc6+ aka >> edf15b4d4b01b565cb5f4fd2e2d08940b9f92e2f and all of the mounts in >> /proc/self/mounts are the same between 4.2.0-rc6 and the RHEL6 stock >> 2.6.32-504.30.3.el6.x86_64, including the cgroups mounted on /cgroup. > > I built a few more kernels just to see if this was some weird backport > thing. The kernels 3.10.86, 3.14.58, 3.18.20, and 4.1.5 all boot and > mount their cgroup filesystems just fine. Granted I kept having to > smack the memory cgroup into being compiled in as the config options > kept changing but otherwise I have not seen any problems. > > So I am very surprised you are having problems. Although I guess I could have saved myself some time by noticing that 4.1.5 was the only one of the kernels with the change backported into it. *Shrug* I don't see the problem and I don't know where to look to see why you are having problems. Eric