linux-kernel - Sysfs nodes deleted and recreated on SMP suspend

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>] [day] [month] [year] [list]

Message-ID: <4E57FD5A.5080005@codeaurora.org>
Date:	Fri, 26 Aug 2011 13:08:58 -0700
From:	Jeff Ohlstein <johlstei@...eaurora.org>
To:	linux-pm@...ts.linux-foundation.org
CC:	LKML <linux-kernel@...r.kernel.org>
Subject: Sysfs nodes deleted and recreated on SMP suspend

So I have been working with the cpufreq sysfs nodes on an SMP system,
and one thing I noticed is that they go away each time I suspend and
resume. This is due to the use of the hotplug mechanism for suspend. I
am able to handle these failures by checking for the error and reopening
the file, but having to do this each time the system suspends seems
unnecessary to me.

Does anyone see any value in making these nodes stay around, at least in
the suspend case of hotplug? I understand that they should go away on
systems where a cpu can actually be physically removed, but if we are
just suspending it seems like we should be as transparent to userspace
as possible.

Jeff
-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
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/