1 |
El 13/7/20 a las 22:07, Francisco Blas Izquierdo Riera (klondike) escribió: |
2 |
> El 13/7/20 a las 21:27, Michał Górny escribió: |
3 |
>> On Mon, 2020-07-13 at 19:33 +0200, Francisco Blas Izquierdo Riera |
4 |
>> (klondike) wrote: |
5 |
>>> El 13/7/20 a las 19:23, Michał Górny escribió: |
6 |
>>>> On Mon, 2020-07-13 at 19:07 +0200, Francisco Blas Izquierdo Riera |
7 |
>>>> (klondike) wrote: |
8 |
>>>>> Hi! |
9 |
>>>>> |
10 |
>>>>> 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. |
11 |
>>>>> |
12 |
>>>>> Affected packages: |
13 |
>>>>> dev-haskell/cryptonite |
14 |
>>>>> dev-libs/json-c |
15 |
>>>>> |
16 |
>>>> I'm sorry but I haven't been following the big rdrand-AMD drama closely. |
17 |
>>>> Does the kernel mitigate broken RDRAND after resume these days? |
18 |
>>>> |
19 |
>>> 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. |
20 |
>>> |
21 |
>> Lemme rephrase: is this something we should be warning our users before |
22 |
>> they enable the flag? I think we should aim to avoid the situation that |
23 |
>> cpuid2cpuflags enables this behind user's backs and their programs |
24 |
>> suddenly break as a result. |
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 |
31 |
> |
32 |
> |
33 |
I have checked also stable versions for other kernel branches and all seem to have the patch icluded. |