linux-kernel - Re: [Bug #13186] cpufreq timer teardown problem

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: <200904261945.11690.rjw@sisk.pl>
Date:	Sun, 26 Apr 2009 19:45:11 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	stable@...nel.org
Subject: Re: [Bug #13186] cpufreq timer teardown problem

On Sunday 26 April 2009, Mathieu Desnoyers wrote:
> * Rafael J. Wysocki (rjw@...k.pl) wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.28 and 2.6.29.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> > be listed and let me know (either way).
> > 
> 
> I've had no news that the patches I proposed has been considered for
> -stable. They fix the teardown problem here. So I guess it's better to
> wait for the patches to get into -stable before we close this bug ?

In fact the bug is closeable as soon as they are in the Linus' tree.  Are they
in it right now?

Thanks,
Rafael
--
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/