mrmondo

For image and photo editing - after many, many years I ditched Adobe Photoshop for Pixelmator Pro - couldn’t be happier, there’s a few workflows that they’re still improving with very regular releases but god damn it’s fast!

* Principal Engineer - Amazon Web Services - Employed Oct 2016 – Present - Employment Duration 1 yr 4 mo

* Intel Corporation - Linux Kernel Engineer - Employed Jun 2008 – Oct 2016 - Employment Duration 8 yrs 5 mos

Source: LinkedIn - https://www.linkedin.com/in/dwmw2/

Note: Also, this is not and please do not turn this into a personal witch-hunt or anything like that, I am just adding context / clarification as to the mailing list thread.

You're completely correct - I did indeed use the wrong terminology and I've done exactly that before with characterising the change in direction of an argument as a straw-man when as you rightly point out - is not correct. Thanks for politely pulling me up on this, I do appreciate it.

As a Kiwi, living in Australia I totally agree and understand, during code review in ops if something crap - I’ll things like ‘hmm, this looks a bit crap, maybe refactor for improved readability?’ Or ‘this has code smell written all over it, we can’t accept this kind of quality into production’ - I could just as easily say ‘Ross, this is shit - just rewrite it’ and my not so hypothetical Ross in this situation would read that - probably laugh, agree and rewrite it the next day OR ask for clarification stating why he doesn’t think it’s shit.

My point is, what matters is the product, the code, the result and the quality there of. The communication around it is entirely based on the relationship and expertise of those around you.

I wish people in this thread would stop turning the discussion into a straw-man argument about Linus’s language and focus their attention to the technical and security problems at hand.

Some people are easily offended, some people easily offend, some people are direct, some people are indirect - get over it.

What matters here is the quality of the code / workarounds that are being presented, by whom and what alternatives they are.

Thank you for saying what I couldn’t put into words.

If you’re worried about ‘cursing’ and you seriously think that it’s something important in the scope of this discussion around security and the grand scale of negligence afoot, I believe you may need to re-evaluate your values.

In fact, the idea that you’re even bringing up such minor language at such a time really disappoints me.

It’s an ideological situation to say the least... but it’s also what we have right know and god damn I’m thankful for it’s beautiful rarity.

Exactly, I’d love to see the state and flux of the Meltdown and Spectre patches for the various Windows kernels.

Thanks for pointing that out - I was under the impression he still worked for intel, before commenting I checked and all the top Google results suggested as much, I’ve corrected my comment.

No worries at all, mailing lists are a PITA to navigate at the best of times.

Could not agree more, unfortunately I’ve seen the latter more often than the former. When you find good management it is truly inspiring however.

Would you rather have the kernel filled with false or botched security?

I think we should count ourselves lucky we have someone so good at spotting bullsh*t like this - and isn’t afraid to call it out as they sees it.

Intel & friends have absolutely disgusted me lately, it could be all to easy to settle for less based on their standards, but let’s not let them set the standard - they’ve shown they can’t be trusted with quality and when they fail - they can’t be trusted to be transparent or even take ownership of the problems they create.

Firefox Beta (58) macOS 10.13.2: WebAssembly.instantiate took 151.9 ms (81.5 MB/s)

Yes, it was very simple to setup, deploy and understand on an ongoing process, BGP is incredibly simple by design.

I’m heading to bed now (AEDST), but check out:

- https://docs.projectcalico.org/latest/getting-started/kubern...

- https://kubernetes.io/docs/tasks/administer-cluster/calico-n...

And there’s plenty of other resources out there. IMO if you’re designing a highly available platform, BGP is one of the simplest parts of that complex system.

In my experience you’re likely to run into much more finicky problems with higher layer systems including failover delays, reliance on casting systems and state drift.

Indeed, completely for fast, simple routing (rather than higher level, more complex failover).

Slightly off topic, but in my experience most (general) internal networking loops stem from mis configured devices bridging networks (desktop level, network device level or VM / SDN)

tldr; from the shizzle (https://share.thesizzle.com.au/sizzleshare/?id=4494):

> “It's only 16 days into 2018 and the Australian federal government is back on their bullshit regarding encryption. Last year, before Senator Brandis was ditched as Attorney General (Christian Porter is the new AG), he was following the UK & USA's "encryption is bad" playbook, and joining law enforcement in saying that due to easy to use, strong encryption, predominately on smartphones, Australia's safety is at risk because it's too hard for police to get into confiscated devices. Anyways, the AG's office said that "legislation to enable Australian law enforcement and security agencies to adapt to the challenges posed by ubiquitous encryption is in an advanced stage of development". How the government manages to screw this up will be exciting and innovative.”

1) Would be neat if you could use this to edit Jekyll / statically generated sites, especially if it had basic git integration.

2) Would be especially useful if it had a mobile client. (Although I know there’s several mobile markdown editing apps, if it had Jekyll / static site generation - that’d be really nice)

I’ve more than a little skeptical of these results, I too am very disappointed in major CPU vendors (especially their PR and management teams), but these results seem more than a little smelly.

I am what I’d consider a heavy iOS user on multiple devices and I don’t believe I’ve honestly noticed any difference at all. If these results were correct, I believe I’d notice at least a 10-15% decrease in performance - but no. What I haven’t looked at is battery life so I cannot comment on that.

Thanks, and on RHEL/CentOS/Fedora:

  dracut -f

To update the intel-ucode package to the system:

- 1. Ensure the existence of /sys/devices/system/cpu/microcode/reload

- 2. Copy intel-ucode directory to /lib/firmware, overwrite the files in /lib/firmware/intel-ucode/

- 3. Write the reload interface to 1 to reload the microcode files, e.g. echo 1 > /sys/devices/system/cpu/microcode/reload

Whoops - s/ATI/AMD

Sorry, force of habit I guess - mods feel free to correct if you notice this as I can’t edit the title after posting.

If nothing else, it sends a clear message of “I wouldn’t trust our product”.

‘M’ just stands for microcontroller, as apposed to ‘A’ for application.

Many / most complex or multitasking embedded devices will use ‘A’ series to meet their processing requirements, e.g. network routing + OS + firmware / OS programming and multiuser processsing.

I probably should have better qualified my use of the term ‘embedded’.

Almost as disgusting as Intel's response.

> "It is important to note that this method is dependent on malware running locally which means it's imperative for users to practice good security hygiene by keeping their software up-to-date and avoid suspicious links or downloads."

If you're running something on your ARM CPU, it's running locally!, they're using careful language to make the problem seem to impact them less than it does and lay the blame on the user.

This affects a huge number of processors out there, not just in phones and tablets but in embedded, industrial and network devices - many of which will never seem workarounds from their OS / software for the hardware fault.

Also OH: "The bug doesn’t happen if you don’t use our product"

> Resolved by software / OS

It's not resolved by, it's mitigated by.

Furthermore, it wasn't mitigated by AMD (or Intel or ARM), it was mitigated by OS / Software vendors that had to spend the time to make workarounds for the hardware's design flaw. It would have been nice to see a nod to such developers for taking the time to help with the problem.

Well said and I think Linus was especially well restrained or perhaps 'careful' with his wording here.

Oh god, it's got a logo: https://meltdownattack.com

"Which systems are affected by Meltdown?

Desktop, Laptop, and Cloud computers may be affected by Meltdown. More technically, every Intel processor which implements out-of-order execution is potentially affected, which is effectively every processor since 1995 (except Intel Itanium and Intel Atom before 2013). We successfully tested Meltdown on Intel processor generations released as early as 2011. Currently, we have only verified Meltdown on Intel processors. At the moment, it is unclear whether ARM and AMD processors are also affected by Meltdown.

Which systems are affected by Spectre?

Almost every system is affected by Spectre: Desktops, Laptops, Cloud Servers, as well as Smartphones. More specifically, all modern processors capable of keeping many instructions in flight are potentially vulnerable. In particular, we have verified Spectre on Intel, AMD, and ARM processors."