linux-kernel - Re: Bad commit backported on the v5.15.y branch ?

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

Message-ID: <2024101632-outspoken-tabby-8ad9@gregkh>
Date: Wed, 16 Oct 2024 16:58:29 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Joel GUITTET <jguittet.opensource@...ekio.com>
Cc: Thorsten Leemhuis <regressions@...mhuis.info>,
	Jay Buddhabhatti <jay.buddhabhatti@....com>,
	Linux kernel regressions list <regressions@...ts.linux.dev>,
	Sasha Levin <sashal@...nel.org>, Stephen Boyd <sboyd@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: Bad commit backported on the v5.15.y branch ?

On Wed, Oct 16, 2024 at 01:13:42PM +0000, Joel GUITTET wrote:
> > Because it has a "Fixes:" tag on it.  Is that tag not correct?
> 
> understood why it's backported. Probably yes. Or maybe another commit should be introduced to not create a new issue.

Perhaps, but I have no clue what is going on here, sorry.

Is this an issue in Linus's tree?  Is it in the other stable releases?
If not, are we missing a change?  Or does the issue show up there as
well?

> > What "original message"?
> 
> My original message in this mailing list, see below commands that show the problem (last line is wrong):
> 
> cat /sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies
> 299999 399999 599999 1199999
> 
> echo 399999 > /sys/devices/system/cpu/cpufreq/policy0/scaling_setspeed
> 
> cat /sys/devices/system/cpu/cpufreq/policy0/scaling_cur_freq
> 399999
> 
> cat /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_cur_freq
> 299999 ====> Should be 399999

Ok, so someone needs to tell me what to do here as I'm confused :)

thanks,

greg k-h