| 1 |
El 13/7/20 a las 21:27, Michał Górny escribió: |
| 2 |
> On Mon, 2020-07-13 at 19:33 +0200, Francisco Blas Izquierdo Riera |
| 3 |
> (klondike) wrote: |
| 4 |
>> El 13/7/20 a las 19:23, Michał Górny escribió: |
| 5 |
>>> On Mon, 2020-07-13 at 19:07 +0200, Francisco Blas Izquierdo Riera |
| 6 |
>>> (klondike) wrote: |
| 7 |
>>>> Hi! |
| 8 |
>>>> |
| 9 |
>>>> 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. |
| 10 |
>>>> |
| 11 |
>>>> Affected packages: |
| 12 |
>>>> dev-haskell/cryptonite |
| 13 |
>>>> dev-libs/json-c |
| 14 |
>>>> |
| 15 |
>>> I'm sorry but I haven't been following the big rdrand-AMD drama closely. |
| 16 |
>>> Does the kernel mitigate broken RDRAND after resume these days? |
| 17 |
>>> |
| 18 |
>> 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. |
| 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 |
You then mean the other rdrand bug. |
| 26 |
|
| 27 |
Yes, current stable linux kernel (5.4.48) in amd64 does include the patch, I'm uncertain about prior kernel branches though but I don't expect many users on that confluence. |
| 28 |
|
| 29 |
The patch: https://lore.kernel.org/linux-doc/776cb5c2d33e7fd0d2893904724c0e52b394f24a.1565817448.git.thomas.lendacky@×××.com/ |
| 30 |
The bug: https://bugzilla.kernel.org/show_bug.cgi?id=85911 |
Archives