linux-kernel - Re: [PATCH v3] x86: i8237: Register based on FADT legacy boot flag

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1522075953.16723.11.camel@linux.intel.com>
Date:   Mon, 26 Mar 2018 15:52:33 +0100
From:   Alan Cox <alan@...ux.intel.com>
To:     Thomas Gleixner <tglx@...utronix.de>,
        Anshuman Gupta <anshuman.gupta@...el.com>
Cc:     glx@...utronix.de, x86@...nel.org, mingo@...hat.com, hpa@...or.com,
        rjw@...ysocki.net, andriy.shevchenko@...ux.intel.com,
        linux-kernel@...r.kernel.org, rajneesh.bhardwaj@...el.com
Subject: Re: [PATCH v3] x86: i8237: Register based on FADT legacy boot flag

> Please explain WHY 2017 is the cut-off date. I still have no clue how
> that
> is decided aside of being a random number.

Because if it's prior to 2017 then it'll almost certainly have those
registers even if the firmware says otherwise. After that point we
think the firmware is going to give valid answers (although the 0xFF
check is actually the important one in reality).

Alan