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  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Thu, 07 May 2020 03:11:25 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Nelson D'Souza <nelson.dsouza@...ux.intel.com>, bp@...en8.de
Cc:     mingo@...hat.com, x86@...nel.org, hpa@...or.com,
        linux-kernel@...r.kernel.org, Tony Luck <tony.luck@...el.com>
Subject: Re: [PATCH v1] x86/cpu/tsx: Change the TSX default from "off" to "auto"

Nelson D'Souza <nelson.dsouza@...ux.intel.com> writes:
> There are now several commercially available processors that have h/w
> fixes for the TSX Async Abort (TAA) issue as indicated by enumerating
> the ARCH_CAPABILITIES "TAA_NO" bit.
>
> Change the default setting to "auto" so that these CPUs will leave
> TSX enabled by default.

You are telling WHAT the patch does, but not the WHY.

It's completely uninteresting whether TAA is fixed in a particular CPU
simply because:

   1) TAA is only one particular issue of TSX.

   2) The main use case for TSX is to accelerate all sorts of
      speculation attacks and other malignances

   3) There is excatly ONE known use case which cares about TSX and we
      already discussed to death that the machines on which that use
      case runs have admins which are capable of adding tsx=on on the
      command line.

So unless you come up with some really convincing argument why this
should be changed, this is not going to happen.

Thanks,

        tglx




Powered by blists - more mailing lists