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]
Message-ID: <1818b3c8-b952-4dba-8b46-a3175adaeb8e@suse.com>
Date: Tue, 18 Feb 2025 14:11:06 +0100
From: Davide Benini <davide.benini@...e.com>
To: Michal Koutný <mkoutny@...e.com>, netdev@...r.kernel.org
Cc: mkubecek@...e.cz
Subject: Re: [PATCH] ss: Tone down cgroup path resolution



On 10/02/25 15:11, Michal Koutný wrote:
> Sockets and cgroups have different lifetimes (e.g. fd passing between
> cgroups) so obtaining a cgroup id to a removed cgroup dir is not an
> error. Furthermore, the message is printed for each such a socket.
> Improve user experience by silencing these specific errors.

Note that if ss has been called with -e (to show detailed socket information) or with --cgroup (to show cgroup information), even if the message "Failed to open cgroup2 by ID" will no longer appear, however the cg_id_to_path() will return a string "unreachable:%llx" and the output will still be similar to

tcp	LISTEN	0	4096	[::]:2049	[::]:*	ino:710321	sk:10da	cgroup:unreachable:8ed7	v6only:1 <->

But I agree that removing the specific error message would be enough to prevent customer concern.

Davide Benini



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ