HWZ Forums

Login Register FAQ Mark Forums Read

All Intel processors affected by memory leaking vulnerability

Like Tree9Likes
Reply
 
LinkBack Thread Tools
Old 04-01-2018, 08:59 AM   #31
Moderator
 
Join Date: Apr 2001
Posts: 51,816
Note: Fanboyism is not welcomed in the forum, 1 warning and 1 infraction already given in this thread for nuisance reply.

Ok for disagreement but no room for disrespectful.
__________________
CSI in HWC, commach spotting idiots

Experience is the teacher of all things.
Julius Caesar
commach is offline   Reply With Quote
Old 04-01-2018, 09:00 AM   #32
Senior Member
 
Join Date: Sep 2007
Posts: 722
Let me drill that down for you:

But what remains to be seen is if this work will be pulled into Linux 4.15 Git or not. We're within three weeks of the executed debut of Linux 4.15.0 stable and it isn't clear if these tip changes will be requested to be pulled into Linux 4.15 or be postponed until the start of the Linux 4.16 kernel merge window, since the safe bulk of the x86 PTI work is already in Git master. Right now the branch name doesn't indicate it's in any fixes/urgent queue nor has there been any pull request yet asking Torvalds to take it into his repository: normally tip.git master is with material for linux-next.

So we'll have to see what ends up happening in the days ahead, but regardless, at least the "AMD patch" is now sitting within a known tree that will eventually flow into the mainline Linux tree whether it be 4.15 or 4.16.
It's pulled in the main repository where it will eventually be considered for merging into mainline. But as of now, it is still not committed for the upcoming 4.15 kernel.

Update: based on Linus's reply in LKML, it's anyone's guess whether AMD's patch is accepted. But it seems like he takes issue with the whole 'treat every x86 processor as affected' initial patch.

Last edited by Rock-kun; 04-01-2018 at 09:03 AM..
Processor
AMD Athlon X2 7750 (I got ripped off! *pissed*)
Mainboard
Biostar GF8200 M2+ TE
Graphics Card
Onboard GeForce 8200...not too shabby.
Memory
2GB DDR2 667GHz SDRAM Kingston Value Ram
Display
19" Acer monitor
Storage
160GB Hitachi Deskstar SATA2
Optical Storage
SAmsung WriteMaster 16X
Casing
*unbranded*
PSU
AcBel 500W
Audio
Onboard. :(
OS
Debian Lenny (Linux kernel 2.6.26.2-AMD64) + Fedora 11

Rock-kun is offline   Reply With Quote
Old 04-01-2018, 09:02 AM   #33
Moderator
 
Join Date: Apr 2001
Posts: 51,816
Update: 1 warning and 2 infractions given in this thread for nuisance replies.
__________________
CSI in HWC, commach spotting idiots

Experience is the teacher of all things.
Julius Caesar
commach is offline   Reply With Quote
Old 04-01-2018, 09:03 AM   #34
Senior Member
 
lamesensei's Avatar
 
Join Date: Aug 2007
Posts: 1,373
I think this episode just proves again the power of AMD's fanboy army, which managed to twist reality... for one day.
Would be the worst marketing spending if they weren't working for free.
intel say amd affected,

amd say amd not affected

both not fanboy + pr machine at work?

who more cb.
Processor
R7 1700
Mainboard
ASRock x370 Fatal1ty Gaming K4
Graphics Card
Gigabyte G1 Gaming GTX 1080
Memory
Cosair Vengeance LPX 16GB 3000 @ XMP 2400
Display
BENQ XL2720Z @ 144Hz
Storage
Samsung 960 PRO NVME 512GB + Samsung 850 EVO 512GB
Casing
NZXT S340 Elite
PSU
Cosair RM 650
Audio
Realtek 1120 + Logi MX Sound 2.0
OS
Windows 10 Home

lamesensei is offline   Reply With Quote
Old 04-01-2018, 09:04 AM   #35
Moderator
 
Join Date: Apr 2001
Posts: 51,816
Update : 1 warning and 3 infractions given.
__________________
CSI in HWC, commach spotting idiots

Experience is the teacher of all things.
Julius Caesar
commach is offline   Reply With Quote
Old 04-01-2018, 09:05 AM   #36
Arch-Supremacy Member
 
wwenze's Avatar
 
Join Date: Dec 2002
Posts: 20,971
More summary from reading:

While with the Linux development code currently, AMD CPUs are marked as insecure and those PTI applied, as covered earlier today, being staged via the tip tree is the much talked about AMD patch. But if that patch will land in time for this month's Linux 4.15 kernel release or be held off until the Linux 4.16 kernel cycle remains to be seen. Regardless, that AMD patch will end up landing some point soon so AMD CPU owners won't be negatively impacted as their hardware appears immune to this latest security issue.
- Reiterating from yesterday's article, systems having PCID (Process Context ID) should lessen the impact of PTI being enabled. (Those interested can check for the presence of "pcid" in their "/proc/cpuinfo" output.) PCID has been present on Intel hardware since the Westmere days, so basically any Sandy Bridge era system or newer should be in better shape. I did manage to pull out an old Lenovo ThinkPad W510 with an Intel Core i7 720QM Clarksfield that is from 2009 and lacks PCID but is affected by this cpu_insecure issue.

- On that old Clarksfield-era ThinkPad I wasn't going to be surprised if the performance was disastrous, but it wound up being better than I had anticipated given all the ongoing drama... In general purpose workloads there was no reportable performance difference in our frequent benchmark test cases. Under I/O, the PTI-using kernel did yield some slower results but not by the margins seen on the newer systems with faster storage. The laptop consumer-grade HDD in this laptop appeared to be the main bottleneck and kernel inefficiencies weren't causing as dramatic slowdowns.

- To some surprise, when carrying out network benchmarks with netperf/iperf3, in at least those contexts PTI didn't have a noticeable impact on the network throughput performance.
Wonder what about USB3 and PCI-E impact tho...
__________________
You can accumulate experience, but whether you learn from it is a separate thing.
Processor
Venice 1.9ghz @ 1.1V on Ninja
Mainboard
MSI MS-7184 Amethyst
Graphics Card
Asus HD4770 Formula
Memory
2GB DDR400 (4x512MB rojak)
Display
Samsung SyncMaster 913V
Storage
WD3200KS on foam
Optical Storage
BenQ DW1650
Casing
Compaq Presario
PSU
Seasonic S12-430
Audio
Audigy -> Zhaolu D3 -> Yulong T-Amp -> Paradigm Atom Monitor v.1 (refoamed)
OS
Windows XP Pro w/SP2

wwenze is online now   Reply With Quote
Old 04-01-2018, 09:07 AM   #37
Senior Member
 
Psycovirus's Avatar
 
Join Date: Jan 2007
Posts: 739
I think this episode just proves again the power of AMD's fanboy army, which managed to twist reality... for one day.
Would be the worst marketing spending if they weren't working for free.
AMD is not affected by the bug that Intel suffers.

Two types of vulnerabilities were documented.

Meltdown flaw affects virtually every microprocessor made by Intel.

The other flaw, Spectre, affects most processors now in use, though the researchers believe this flaw is more difficult to exploit. There is no known fix for it.

From this article

Google is mentioning two different vulnerabilities. Intel bug still remains as the top priority to fix.
__________________
"The human eye can see far beyond a measly 30 or 60FPS"
Processor
AMD Ryzen R7 @ 3.9 GHz - Cryorig R1 Universal
Mainboard
ASRock X370 Killer SLI/ac
Graphics Card
EVGA GTX 1080 Ti FTW3
Memory
Corsair Vengeance LED 3200C16 @ 2933C16
Display
34U100 34" 3440x1440@100Hz Freesync
Storage
Samsung 960 EVO 500GB m.2 / Samsung 850 Evo 500GB m.2
Casing
Fractal Design Define R6
PSU
Seasonic Focus+ 650W Modular
Audio
S.M.S.L AD-18 + Micca MB42X + 8" Powered Sub / HD6XX + Fiio E09K+E07K
OS
Windows 10 Pro x64

Psycovirus is offline   Reply With Quote
Old 04-01-2018, 09:07 AM   #38
Arch-Supremacy Member
 
wwenze's Avatar
 
Join Date: Dec 2002
Posts: 20,971
I know Google claims ARM is also affected, but I still don't believe ARM has the computational power to drive datacentres and public clouds.
Oh that you'd be wrong xia.

Those systems powered by nVidia / ARM combo?
__________________
You can accumulate experience, but whether you learn from it is a separate thing.
Processor
Venice 1.9ghz @ 1.1V on Ninja
Mainboard
MSI MS-7184 Amethyst
Graphics Card
Asus HD4770 Formula
Memory
2GB DDR400 (4x512MB rojak)
Display
Samsung SyncMaster 913V
Storage
WD3200KS on foam
Optical Storage
BenQ DW1650
Casing
Compaq Presario
PSU
Seasonic S12-430
Audio
Audigy -> Zhaolu D3 -> Yulong T-Amp -> Paradigm Atom Monitor v.1 (refoamed)
OS
Windows XP Pro w/SP2

wwenze is online now   Reply With Quote
Old 04-01-2018, 09:08 AM   #39
Supremacy Member
 
Join Date: Mar 2002
Posts: 5,622
intel say amd affected,

amd say amd not affected

both not fanboy + pr machine at work?

who more cb.
There are two seperate issues. It is still only a rumour that AMD chips have the vunerability. We can assume they do not since there has been no explicit work on closing the gap specifically for AMD.

The second issue is that there is no guarantee right now that the Intel patch will not affect AMD chip performance. Yes, there is a workaround, but officially this has not been accepted. So AMD will get screwed over in the short term too until the patches get refined over time. But it is a real concern that even AMD fanboys have voiced out.
Processor
2.0 GHz Intel Core 2 Duo
Graphics Card
Intel GMA 950 graphics processor
Memory
1.5 GB 667 MHz DDR2 Ram
Display
13.3 " TFT
Storage
80GB 5400 rpm Serial ATA hard disk drive
Optical Storage
24x slot-loading Combo drive (DVD-ROM/CD-RW)
OS
OS X Leopard

furyoo is online now   Reply With Quote
Old 04-01-2018, 09:39 AM   #40
Supremacy Member
 
Ark Law's Avatar
 
Join Date: Jan 2013
Posts: 8,541
TLDR of a TLDR;



Here's Intel's press release
Processor
i5 7300U vPro Powered By Intel
Graphics Card
HD620 Fabricated By Intel
Memory
24GB 2133MHz Fueled By Micron
Storage
256GB Sponsored By Toshiba
Casing
Dell Latitude 7480 Made By Quanta/Compal
PSU
65W Class VI Courtesy Of Chicony Power Technology
OS
Spyware 10 Pro Formulated By Microsoft

Ark Law is offline   Reply With Quote
Old 04-01-2018, 09:39 AM   #41
Senior Member
 
Blindaim's Avatar
 
Join Date: Aug 2007
Posts: 2,244
https://www.phoronix.com/scan.php?pa...isable-x86-PTI

AMD Performance won't be hit in Linux.

Update: Linus Torvalds has now ended up pulling the latest PTI fixes that also include the change to disable page table isolation for now on all AMD CPUs. The commit is in mainline for Linux 4.15 along with a few basic fixes and ensuring PAGE_TABLE_ISOLATION is enabled by default.

Kernel developer Thomas Gleixner wrote in the pull request of disabling KPTI on AMD hardware, "Not necessarily a fix, but if AMD is so confident that they are not affected, then we should not burden users with the overhead."
__________________
We're made of stardust and connected to each other

Last edited by Blindaim; 04-01-2018 at 01:26 PM..
Blindaim is offline   Reply With Quote
Old 04-01-2018, 09:46 AM   #42
Senior Member
 
Psycovirus's Avatar
 
Join Date: Jan 2007
Posts: 739
TLDR of a TLDR;



Here's Intel's press release
Haha. Intel in full damage control mode.

I really hope AMD EYPC will succeed so that there's better competition in the server space and not being monopolized by Intel.
__________________
"The human eye can see far beyond a measly 30 or 60FPS"
Processor
AMD Ryzen R7 @ 3.9 GHz - Cryorig R1 Universal
Mainboard
ASRock X370 Killer SLI/ac
Graphics Card
EVGA GTX 1080 Ti FTW3
Memory
Corsair Vengeance LED 3200C16 @ 2933C16
Display
34U100 34" 3440x1440@100Hz Freesync
Storage
Samsung 960 EVO 500GB m.2 / Samsung 850 Evo 500GB m.2
Casing
Fractal Design Define R6
PSU
Seasonic Focus+ 650W Modular
Audio
S.M.S.L AD-18 + Micca MB42X + 8" Powered Sub / HD6XX + Fiio E09K+E07K
OS
Windows 10 Pro x64

Psycovirus is offline   Reply With Quote
Old 04-01-2018, 10:25 AM   #43
Arch-Supremacy Member
 
wwenze's Avatar
 
Join Date: Dec 2002
Posts: 20,971
People also said PS4 won't get exploit...

Is just how much effort hackers want to put in I guess. This cost vs benefit race has always been the spotlight when it comes to encryption.

And thanks to *cough*Windows*cough*Google*cough*Facebook*cough*fkingUber*cough* hackers have never needed to resort to hardware exploits. But yes, access to unauthorized memory location is always the start of hacking.

Haha. Intel in full damage control mode.

I really hope AMD EYPC will succeed so that there's better competition in the server space and not being monopolized by Intel.
DNA argument. More variety, less effect.

But DNA also means survival of the fittest and that's what killed all the rest of the makers...
__________________
You can accumulate experience, but whether you learn from it is a separate thing.
Processor
Venice 1.9ghz @ 1.1V on Ninja
Mainboard
MSI MS-7184 Amethyst
Graphics Card
Asus HD4770 Formula
Memory
2GB DDR400 (4x512MB rojak)
Display
Samsung SyncMaster 913V
Storage
WD3200KS on foam
Optical Storage
BenQ DW1650
Casing
Compaq Presario
PSU
Seasonic S12-430
Audio
Audigy -> Zhaolu D3 -> Yulong T-Amp -> Paradigm Atom Monitor v.1 (refoamed)
OS
Windows XP Pro w/SP2

wwenze is online now   Reply With Quote
Old 04-01-2018, 10:53 AM   #44
High Supremacy Member
 
haylui's Avatar
 
Join Date: Jul 2006
Posts: 27,100
https://www.amd.com/en/corporate/speculative-execution

AMD official responses on the vulnerability.
also need to take with a pinch of salt?
Processor
AMD Phenom II X6 1090T + CM V6GT + Corsair 2 x SP120 Perf
Mainboard
MSI 870-G54
Graphics Card
Sapphire HD7970
Memory
Kingston KVM 2x4GB 1333MHz
Display
Philips 220CW
Storage
60GB Kingston SSD+500GB WD Blue + 250GB seagate
Optical Storage
Samsung 22x DVDRW
Casing
ThermalTake Level 10GTS
PSU
FSP AURUM 92+ Series PT-650M
Audio
VIA VT1828S + Logitech X-230
OS
Windows 7 Pro

haylui is offline   Reply With Quote
Old 04-01-2018, 12:11 PM   #45
High Supremacy Member
 
Ferolare's Avatar
 
Join Date: Feb 2007
Posts: 47,229
all take with a pinch of salt until Kernel 4.15 rolls out bah

as for me: i'll twiddle my thumb until Mint 19 or 18.04LTS bah

(but my money is on no impact whatsoever on my media pc )
__________________
Still waiting for the perfect AM4 motherboard
Processor
Intel Core i5-4460
Mainboard
ASRock B85M Pro4
Memory
G.SKILL RipjawsX F3-14900CL9D-8GBXL @ DDR3-1600 9-9-9-24-2N
Display
Panasonic VIERA TH-L39EM5S
Storage
ZOTAC T500 120GB
Casing
Thermaltake Commander MS-I Snow Edition
PSU
FSP ECO 400
Audio
Acoustic Energy Aego
OS
Linux Mint 18.3

Ferolare is offline   Reply With Quote
Reply
Important Forum Advisory Note
This forum is moderated by volunteer moderators who will react only to members' feedback on posts. Moderators are not employees or representatives of HWZ. Forum members and moderators are responsible for their own posts.

Please refer to our Terms of Service for more information.


Thread Tools

Posting Rules

Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are On