linux-kernel - Re: [PATCH] fix cpufreq

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: <20070322171436.GM15364@redhat.com>
Date:	Thu, 22 Mar 2007 13:14:36 -0400
From:	Dave Jones <davej@...hat.com>
To:	Andrew Morton <akpm@...ux-foundation.org>,
	Greg KH <gregkh@...e.de>, Alexey Dobriyan <adobriyan@...ru>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] fix cpufreq_stats attrs removal

On Thu, Mar 22, 2007 at 06:02:01PM +0100, Mattia Dongili wrote:

 > The problem is cpufreq_stats doesn't know when a cpufreq driver is
 > removed and doesn't cleanup. I guess this affects any setup with
 > cpufreq_stats.
 > The attached patch seems to solve both symptoms and yes... it's quite
 > invasive as it introduce one more cpufreq policy notification (REMOVED).
 > 
 > BTW: the patch is against .21-rc4-mm1 but applies with some fuzz to
 > 2.6.20 too

Alternatively, as it's just debug functionality, we could just
mark it unsafe for rmmod, which is nastier, but a lot less invasive
to the non-debug code.

	Dave

-- 
http://www.codemonkey.org.uk
-
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/