linux-kernel - [PATCH stable 0/1] x86: aperfmperf: bug report

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

Date:   Fri, 21 Oct 2022 10:17:39 +0800
From:   Yipeng Zou <zouyipeng@...wei.com>
To:     <tglx@...utronix.de>, <bp@...en8.de>, <mingo@...hat.com>,
        <x86@...nel.org>, <hpa@...or.com>, <rafael.j.wysocki@...el.com>,
        <linux-kernel@...r.kernel.org>
CC:     Yipeng Zou <zouyipeng@...wei.com>
Subject: [PATCH stable 0/1] x86: aperfmperf: bug report

Recently i was doing some work about calculating CPU frequency on x86 on
stable branch linux-5.10.y, and there is a problem which i descrip in
the commit message.

I've noticed that it has been abandoned on the mainline. On the mainline
it becomes to update [a,m]cnt in timer code with HZ frequency, and it is
actually calculated at the time of reading the cpu freqency. This solves
the problem above.

So, Are there other reasons why the stable branch doesn't have these
changes?, this patch is just to ask how we plan to fix it.

Yipeng Zou (1):
  x86: aperfmperf: fix overflow problem in the concurrency scenario

 arch/x86/kernel/cpu/aperfmperf.c | 4 ----
 1 file changed, 4 deletions(-)

-- 
2.17.1