linux-kernel - pm_idle generic register/unregister

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: <1205218954.27299.91.camel@perihelion>
Date:	Tue, 11 Mar 2008 03:02:34 -0400
From:	Jon Masters <jonathan@...masters.org>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: pm_idle generic register/unregister

Yo,

I'm working on a patch (needed for the Real Time tree) to cleanup use of
the pm_idle pointer, something each architecture defines and optionally
calls from within the CPU idle loop, if it's defined. The problem is
that there's a classical bug (which has existed for quite some time)
whenever a function providing that pointer is unloaded from under it.

So, I'm proposing an ordered list of pm_idle functions with a
register/unregister function to ensure safe access. Anyway, before I
post that, does anyone have a good reason for why things are as they are
currently in the kernel with respect to the pm_idle stuff? Cruftiness?

Jon.

--
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/