linux-kernel - Re: sysfs and power management

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: <20101027124816.7087436a@linux.intel.com>
Date:	Wed, 27 Oct 2010 12:48:16 +0100
From:	Alan Cox <alan@...ux.intel.com>
To:	samu.p.onkalo@...ia.com
Cc:	gregkh@...e.de, Andrew Morton <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: sysfs and power management

> I started to wonder if it makes sense to enhance sysfs so that it
> optionally prodives open / close call backs. Internally sysfs has
> some bookkeeping about the refcount but this is not visible to the
> driver. Of course majority of the sysfs users doesn't need that at all
> and for them this is just overhead. 

I think we need it. There doesn't need to be much overhead however as
there is no need (or sense) in providing per sysfs node open/close
hooks.

The pm layer also lacks a clean race-free way to actually ascertain
when the device was last kicked out of pm saving.
--
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/