Missing expected images:
Server dvd i386
Workstation live i386
Server boot i386
Kde live i386
Failed openQA tests: 97/128 (x86_64), 1/2 (arm)
New failures (same test did not fail in Rawhide-20180102.n.0):
ID: 183659 Test: x86_64 Server-boot-iso install_default@uefi
URL: https://openqa.fedo
The following Fedora 27 Security updates need testing:
Age URL
39 https://bodhi.fedoraproject.org/updates/FEDORA-2017-15efa72a0c
docker-1.13.1-44.git584d391.fc27
35 https://bodhi.fedoraproject.org/updates/FEDORA-2017-913288e9a9
mongodb-3.4.10-1.fc27
32 https://bodhi.fedoraproject.o
On Wed, 2018-01-03 at 20:43 +, Fedora compose checker wrote:
> Missing expected images:
>
> Server dvd i386
> Workstation live i386
> Server boot i386
> Kde live i386
These are due to:
https://github.com/rhinstaller/lorax/pull/299
Once a lorax package build with that fix shows up in Rawhide
On Wed, 03 Jan 2018 16:39:34 -0800
Adam Williamson wrote:
> On Wed, 2018-01-03 at 15:02 -0800, Adam Williamson wrote:
> > Hi folks!
> >
> > So you might have read some stories today about an issue that's
> > being described as a design flaw in some CPUs which makes it
> > possible for unprivileg
On Wed, 03 Jan 2018 15:02:11 -0800
Adam Williamson wrote:
> * We know that the fix can lead to reduced performance in some cases
> (this affects synthetic benchmarks rather more than real-world
> performance). The kernel team thinks the fix is sufficiently important
> that it should go out despit
On 01/04/18 09:13, stan wrote:
> Again, from my reading on the web this only affects Intel CPUs of the
> last decade. So, no other manufacturer or architecture needs to have
> the fix applied.
I don't know about that. Going to https://meltdownattack.com/ it reads
Which systems are affected
On Wed, 2018-01-03 at 18:13 -0700, stan wrote:
> On Wed, 03 Jan 2018 15:02:11 -0800
> Adam Williamson wrote:
>
> > * We know that the fix can lead to reduced performance in some cases
> > (this affects synthetic benchmarks rather more than real-world
> > performance). The kernel team thinks the f
On Thu, 4 Jan 2018 09:23:58 +0800
Ed Greshko wrote:
> I don't know about that. Going to https://meltdownattack.com/ it
> reads
>
> Which systems are affected by Meltdown?
> Desktop, Laptop, and Cloud computers may be affected by Meltdown.
> More technically, every Intel processor which impl
On Thu, 2018-01-04 at 01:35 +, Philip Kovacs wrote:
> Any word on the performance hit before you push to stable? Is it
> discernible?
So far as I've read, the general consensus is that you're probably not
going to notice it in most usage. Some specific synthetic benchmarks
are showing impac
On Wed, 2018-01-03 at 17:48 -0800, Adam Williamson wrote:
>
> This is certainly not correct. Both the Google researchers and Red
> Hat's security team have stated that many other CPUs and CPU families
> are affected. ARM has already released a statement acknowledging that
> several of their CPUs,
On Thu, 4 Jan 2018 09:23:58 +0800
Ed Greshko wrote:
> And how about
> https://www.windowscentral.com/all-modern-processors-impacted-new-meltdown-and-spectre-exploits
>
> ?
My comments were directed at Meltdown (formerly called Kaiser, now
called kopti). I saw nothing about spectre, so I will
On Wed, 2018-01-03 at 19:04 -0700, stan wrote:
> On Thu, 4 Jan 2018 09:23:58 +0800
> Ed Greshko wrote:
>
> > And how about
> > https://www.windowscentral.com/all-modern-processors-impacted-new-meltdown-and-spectre-exploits
> >
> > ?
>
> My comments were directed at Meltdown (formerly called K
On Wed, 03 Jan 2018 17:59:11 -0800
Adam Williamson wrote:
> On Wed, 2018-01-03 at 17:48 -0800, Adam Williamson wrote:
> > The initial reporting that only Intel CPUs were affected was
> > entirely wrong.
I think you are conflating exploits. The original exploit, called
meltdown or kaiser or ko
On Wed, 2018-01-03 at 19:31 -0700, stan wrote:
> On Wed, 03 Jan 2018 17:59:11 -0800
> Adam Williamson wrote:
>
> > On Wed, 2018-01-03 at 17:48 -0800, Adam Williamson wrote:
> > > The initial reporting that only Intel CPUs were affected was
> > > entirely wrong.
>
> I think you are conflating e
On Thu, 4 Jan 2018 09:23:58 +0800
Ed Greshko wrote:
> And how about
> https://www.windowscentral.com/all-modern-processors-impacted-new-meltdown-and-spectre-exploits
>
> ?
> Unless there is a significant performance hit isn't it better to just
> be safe and make it for all?
Wow, SPECTRE is
On Wed, 03 Jan 2018 18:45:14 -0800
Adam Williamson wrote:
> Rather, I am not concerning myself with individual exploits with cute
> names, because that's sort of a silly way to look at things, in my
> opinion. The actual truth of how this went down - as I understand it -
> is just not "there was
On Thu, Jan 4, 2018 at 2:49 AM, stan wrote:
> On Thu, 4 Jan 2018 09:23:58 +0800
> Ed Greshko wrote:
>
>
>> And how about
>> https://www.windowscentral.com/all-modern-processors-impacted-new-meltdown-and-spectre-exploits
>> ?
>
>> Unless there is a significant performance hit isn't it better to ju
On Wed, Jan 03, 2018 at 06:06:11PM -0700, stan wrote:
> It turns out that AMD processors are not affected by this problem.
This is not completely clear. AMD processors seem to be not affected by
at least some forms of the "Meltdown" variant of the problem; I don't
think we can confidently state an
On Wed, 3 Jan 2018 22:24:03 -0500
Matthew Miller wrote:
> On Wed, Jan 03, 2018 at 06:06:11PM -0700, stan wrote:
> > It turns out that AMD processors are not affected by this problem.
>
> This is not completely clear. AMD processors seem to be not affected
> by at least some forms of the "Meltd
On Thu, 4 Jan 2018 02:59:57 +
Peter Robinson wrote:
> In the brief look I took at the patches the fixes are only applied if
> the processor is vulnerable, so in the case of meltdown, it's only
> applied to the affected processors. This is generally the case with
> most CPU HW errata, whether
Missing expected images:
Server dvd i386
Workstation live i386
Server boot i386
Kde live i386
Failed openQA tests: 15/128 (x86_64), 1/2 (arm)
Old failures (same test failed in Rawhide-20180102.n.0):
ID: 183999 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller
URL: https://op
21 matches
Mail list logo
