-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Simon Gaiser:
[...]
>>> - Installing the patched gcc required manual intervention in my chroot
>>>(didn't tried a fresh chroot yet). For some reasons it only wanted to
>>>install it when I told dnf explicitly to install the updated gcc and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, Feb 26, 2018 at 01:32:00PM +, Simon Gaiser wrote:
> Marek Marczykowski-Górecki:
> [...]
> > I'd go with backporting patches to original Fedora's gcc.
>
> Fedora uses their own gcc snapshot in their package (i.e. not an
> upstream
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Marek Marczykowski-Górecki:
[...]
> I'd go with backporting patches to original Fedora's gcc.
Fedora uses their own gcc snapshot in their package (i.e. not an
upstream tarball). AFAICS Fedora does not host it directly anywhere.
Where should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Reg Tiangha:
> On 02/25/2018 01:53 PM, Simon Gaiser wrote:
>> - The Fedora gcc package build seems to be flacky. It failed twice for
>>me with different errors (both verry likely unrelated to the backport
>>patches). Assigning a lot of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Marek Marczykowski-Górecki:
> On Sun, Feb 25, 2018 at 08:53:00PM +, Simon Gaiser wrote:
>> Marek Marczykowski-Górecki:
>>> On Fri, Feb 23, 2018 at 03:27:38PM -0700, Reg Tiangha wrote:
I've noticed that Xen has updated the XSA-254 advisory
On 02/25/2018 01:53 PM, Simon Gaiser wrote:
> - The Fedora gcc package build seems to be flacky. It failed twice for
>me with different errors (both verry likely unrelated to the backport
>patches). Assigning a lot of memory to the build VM got it working
>... And I noticed that a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Feb 25, 2018 at 08:53:00PM +, Simon Gaiser wrote:
> Marek Marczykowski-Górecki:
> > On Fri, Feb 23, 2018 at 03:27:38PM -0700, Reg Tiangha wrote:
> >> I've noticed that Xen has updated the XSA-254 advisory with Spectre v2
> >> mitigations
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Marek Marczykowski-Górecki:
> On Fri, Feb 23, 2018 at 03:27:38PM -0700, Reg Tiangha wrote:
>> I've noticed that Xen has updated the XSA-254 advisory with Spectre v2
>> mitigations for Xen 4.6-4.10. I know we'd have to figure out how to
>> backport
On 02/23/2018 04:08 PM, Marek Marczykowski-Górecki wrote:
> Simon, can you take a look at it? We'll probably need to put patched gcc
> to linux-dom0-updates repository (if newer Fedora has patched gcc and
> it's possible to build that src.rpm on older Fedora), or add separate
> repository with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, Feb 23, 2018 at 03:27:38PM -0700, Reg Tiangha wrote:
> I've noticed that Xen has updated the XSA-254 advisory with Spectre v2
> mitigations for Xen 4.6-4.10. I know we'd have to figure out how to
> backport Retpoline compatible compilers to
On Fri, February 23, 2018 10:27 pm, Reg Tiangha wrote:
> And a side question about qubes-builder: Does it build in a chroot? I'd
> like to attempt to backport a build environment that has a
> retpoline-enabled version of gcc, and I'm wondering if I could just bypass
> qubes-builder entirely and
On 01/24/2018 04:29 AM, Andrew David Wong wrote:
## Qubes 3.2
Previously, we had planned to release an update for Qubes 3.2 that would
have made almost all VMs run in PVH mode by backporting support for this
mode from Qubes 4.0.
Out of curiosity, is this still going to happen? I would love
On 01/25/2018 09:03 PM, Rich Persaud wrote:
This OpenXT wiki page aggregates evolving info from upstream projects and
vendor disclosures on Spectre/Meltdown:
https://openxt.atlassian.net/wiki/spaces/DC/pages/397967361/Meltdown+and+Spectre+mitigations+for+Xen+Linux+and+Windows
It links to an
This OpenXT wiki page aggregates evolving info from upstream projects and
vendor disclosures on Spectre/Meltdown:
https://openxt.atlassian.net/wiki/spaces/DC/pages/397967361/Meltdown+and+Spectre+mitigations+for+Xen+Linux+and+Windows
It links to an exportable spreadsheet that tracks guest
14 matches
Mail list logo
