On 02/09/2018 09:46 PM, Philip Prindeville wrote:
>
>
>> On Jan 18, 2018, at 2:15 PM, Hauke Mehrtens wrote:
>>
>> On 01/18/2018 01:51 PM, Nick Lowe wrote:
>>> Does an update to the Kernel, 4.9.77 and 4.14.14 need to be made to
>>> properly address this? There are fixes to mitigate Spectre.
>>
>>
> On Jan 18, 2018, at 2:15 PM, Hauke Mehrtens wrote:
>
> On 01/18/2018 01:51 PM, Nick Lowe wrote:
>> Does an update to the Kernel, 4.9.77 and 4.14.14 need to be made to
>> properly address this? There are fixes to mitigate Spectre.
>
> We even need a patch for GCC which will be in GCC 8 and 7.
Hi,
There's a backport to GCC 5.5 here:
https://github.com/hjl-tools/gcc/commits/hjl/indirect/gcc-5-branch/master
Cheers,
Nick
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Should be resolved in 4.4.113 and 4.9.78 that are now available.
Cheers,
Nick
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Yup, this affects both 4.4.112 and 4.9.77
A fix for this has been queued by Greg for both 4.4.113 and 4.9.78
It does not affect 4.14.14
Cheers,
Nick
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/le
Ironically, 4.4.112 is reporting similar behaviour:
# grep . /sys/devices/system/cpu/vulnerabilities/*
/sys/devices/system/cpu/vulnerabilities/meltdown:Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v1:Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Vulnerable
root@PC En
Hi,
Thanks! I have done so and this is now queued for 4.9.y and 4.4.y
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=d28663e54705568523979ab8097b9672ee79b17f
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=8ea729c00403414d744
On 01/21/2018 01:07 PM, Nick Lowe wrote:
> Hi Arjen,
>
> The point I was making is that we see:
>
> root@LEDE:/sys/devices/system/cpu/vulnerabilities# cat meltdown
> Vulnerable
>
> This should not be marked as vulnerable and it is being.
>
> Cheers,
>
> Nick
>
> On Sun, Jan 21, 2018 at 12:04
Hi Arjen,
The point I was making is that we see:
root@LEDE:/sys/devices/system/cpu/vulnerabilities# cat meltdown
Vulnerable
This should not be marked as vulnerable and it is being.
Cheers,
Nick
On Sun, Jan 21, 2018 at 12:04 PM, Arjen de Korte
wrote:
> Citeren Nick Lowe :
>
>
>> Yes, compiler
Citeren Nick Lowe :
Yes, compiler updates will ultimately be necessary to properly close this.
We can see for now with 4.9.77:
root@LEDE:/sys/devices/system/cpu/vulnerabilities# cat spectre_v2
Vulnerable: Minimal AMD ASM retpoline
AMD processors are also incorrectly being marked as being vuln
Yes, compiler updates will ultimately be necessary to properly close this.
We can see for now with 4.9.77:
root@LEDE:/sys/devices/system/cpu/vulnerabilities# cat spectre_v2
Vulnerable: Minimal AMD ASM retpoline
AMD processors are also incorrectly being marked as being vulnerable
to Meltdown. On
John Crispin wrote:
On 17/01/18 20:41, Zoltan HERPAI wrote:
Hi,
This series will add support for microcode update on x86 targets,
in light of the recent security issues.
While other distributions use an early initramfs approach to update
the microcode as early as possible, in OpenWrt the ear
On 01/18/2018 11:41 PM, Zoltan HERPAI wrote:
>
>
> On Thu, 18 Jan 2018, Hauke Mehrtens wrote:
>
>> On 01/18/2018 01:51 PM, Nick Lowe wrote:
>>> Does an update to the Kernel, 4.9.77 and 4.14.14 need to be made to
>>> properly address this? There are fixes to mitigate Spectre.
>>
>> We even need a
On Thu, 18 Jan 2018, Hauke Mehrtens wrote:
On 01/18/2018 01:51 PM, Nick Lowe wrote:
Does an update to the Kernel, 4.9.77 and 4.14.14 need to be made to
properly address this? There are fixes to mitigate Spectre.
We even need a patch for GCC which will be in GCC 8 and 7.3.
For master we shou
On 01/18/2018 01:51 PM, Nick Lowe wrote:
> Does an update to the Kernel, 4.9.77 and 4.14.14 need to be made to
> properly address this? There are fixes to mitigate Spectre.
We even need a patch for GCC which will be in GCC 8 and 7.3.
For master we should backport it to GCC 5.5, but what do we want
Does an update to the Kernel, 4.9.77 and 4.14.14 need to be made to
properly address this? There are fixes to mitigate Spectre.
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
On 17/01/18 20:41, Zoltan HERPAI wrote:
Hi,
This series will add support for microcode update on x86 targets,
in light of the recent security issues.
While other distributions use an early initramfs approach to update
the microcode as early as possible, in OpenWrt the earliest place
where we
On January 17, 2018 11:41:01 AM PST, Zoltan HERPAI wrote:
>Hi,
>
>This series will add support for microcode update on x86 targets,
>in light of the recent security issues.
>
>While other distributions use an early initramfs approach to update
>the microcode as early as possible, in OpenWrt the e
18 matches
Mail list logo
