| 1 |
On Mon, 2020-07-13 at 19:33 +0200, Francisco Blas Izquierdo Riera |
| 2 |
(klondike) wrote: |
| 3 |
> El 13/7/20 a las 19:23, Michał Górny escribió: |
| 4 |
> > On Mon, 2020-07-13 at 19:07 +0200, Francisco Blas Izquierdo Riera |
| 5 |
> > (klondike) wrote: |
| 6 |
> > > Hi! |
| 7 |
> > > |
| 8 |
> > > We have currently two packages that have USE cpu-flags-x86-rdrand as there is no USE_EXPAND version available. This pattern is likely to confuse users as they may not be aware of the difference between dashes and underscores. |
| 9 |
> > > |
| 10 |
> > > Affected packages: |
| 11 |
> > > dev-haskell/cryptonite |
| 12 |
> > > dev-libs/json-c |
| 13 |
> > > |
| 14 |
> > I'm sorry but I haven't been following the big rdrand-AMD drama closely. |
| 15 |
> > Does the kernel mitigate broken RDRAND after resume these days? |
| 16 |
> > |
| 17 |
> AGESA patches do exist to address this issue: https://www.reddit.com/r/Amd/comments/cmza34/agesa_1003_abb_fixes_rdrandrdseed/ I suspect AMD microcode does too. |
| 18 |
> |
| 19 |
|
| 20 |
Lemme rephrase: is this something we should be warning our users before |
| 21 |
they enable the flag? I think we should aim to avoid the situation that |
| 22 |
cpuid2cpuflags enables this behind user's backs and their programs |
| 23 |
suddenly break as a result. |
| 24 |
|
| 25 |
-- |
| 26 |
Best regards, |
| 27 |
Michał Górny |
Archives