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: Fri, 2 Feb 2024 07:10:22 -1000
From: Tejun Heo <tj@...nel.org>
To: "brookxu.cn" <brookxu.cn@...il.com>
Cc: longman@...hat.com, lizefan.x@...edance.com, hannes@...xchg.org,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] cpuset: remove /proc/PID/cpuset

On Fri, Feb 02, 2024 at 06:49:11PM +0800, brookxu.cn wrote:
> From: Chunguang Xu <chunguang.xu@...pee.com>
> 
> Now we can get all cgroup paths from /proc/PID/cgroup for
> a long time, so it maybe useless to keep /proc/PID/cpuset,
> besides the path get from /proc/PID/cpuset is not consistent
> with /proc/PID/cgroup in default hierarchy, so now we may
> can safely remove /proc/PID/cpuset to avoid the mismatch.
> 
> root@...t:~# cat /proc/1186/cgroup
> 0::/system.slice/lmeter.service

I don't think we can remove it, unfortunately. We can try to deprecate it
and annoy people who use it over time and eventually remove it, but I don't
see a reason why we should do that. It doesn't get in anyone's way, so let's
let it be.

Thanks.

-- 
tejun

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ