# Re: \[CFT\]\[PATCH 09/10\] sysfs: Create mountpoints with sysfs\_create\_empty\_dir

- List: linux-api
- 1 message, 1 author
- Page: https://ratatoskr.run/linux-api/2015/08/98511/t

## Re: \[CFT\]\[PATCH 09/10\] sysfs: Create mountpoints with sysfs\_create\_empty\_dir

- From: Eric W. Biederman \<hidden\>
- Date: 2015-08-12 04:04:28 
- Message: https://ratatoskr.run/linux-api/2015/08/98511.md

```text
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
```