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: <CALjTZvYFTS4G4CZnFqHU+H7v4_0w-hFB_wV6Z1Ksy+nQ6M6_5A@mail.gmail.com>
Date:   Fri, 7 Apr 2023 19:57:59 +0100
From:   Rui Salvaterra <rsalvaterra@...il.com>
To:     srinivas pandruvada <srinivas.pandruvada@...ux.intel.com>
Cc:     Borislav Petkov <bp@...en8.de>, x86@...nel.org,
        linux-kernel@...r.kernel.org,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        Daniel Lezcano <daniel.lezcano@...aro.org>,
        Amit Kucheria <amitk@...nel.org>,
        Zhang Rui <rui.zhang@...el.com>, linux-pm@...r.kernel.org
Subject: Re: [BUG?] unchecked MSR access error: WRMSR to 0x19c

Hi, Srinivas,

On Thu, 6 Apr 2023 at 23:31, srinivas pandruvada
<srinivas.pandruvada@...ux.intel.com> wrote:
>
> Please send output of : cpuid -1

Attached.

> Also please try this:
>
> #wrmsr 0x19c 0xaaa8
> This should give "wrmsr: CPU 0 cannot set MSR 0x0000019c to 0x000000000000aaa8

Indeed, it does:

wrmsr: CPU 0 cannot set MSR 0x0000019c to 0x000000000000aaa8

> #wrmsr 0x19c 0x0aa8
>
> I think this will not return error.

Correct, no error writing 0x0aa8.

I'll soon test the patch you sent me.

Kind regards,
Rui

View attachment "cpuid.txt" of type "text/plain" (27032 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ