Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

+ - Ext4 Corruption Bug Found in Linux

Submitted by jones_supa
jones_supa writes: It seems that an Ext4 data corruption bug has slipped into Linux at some point. Josh Triplett warns about the issue in the Debian bug tracking system. His server machine already experienced major damage to the filesystem. A patch has already been created, which describes the situation as follows: "Currently it is possible to lose whole file system block worth of data when we hit the specific interaction with unwritten and delayed extents in status extent tree. [...] For now we can fix this by simply not allowing to set delayed status on written extent in the extent status tree. Also add WARN_ON() to make sure that we notice if this happens in the future." Consider applying the patch (or simply upgrading to Linux 4.0.3 which incorporates the patch) to prevent filesystem corruption.

Comment: Re:No. (Score 1) 507

by jhantin (#49700769) Attached to: Is Agile Development a Failing Concept?

we the developers were the first ones to go "Woah there, Peaches".


There aren't so many gender-neutral horse names to choose from. You seem quick to judge - perhaps he alternates between fillies and stallions in his horse metaphors.

These discussions usually continue long after the horse is beaten to death - call it blunt metaphors trauma.

Comment: Re:magic ingredient: perfluorooctyltriethoxysilane (Score 1) 87

This uses POTS, not FDTS, so there are ethoxy groups instead of chlorine atoms bound to the silicon. Still flammable, but POTS is innocuous enough that it's used to coat pigment particles in cosmetics.

I suspect even FDTS gets a lot less nasty once a coating settles in. R1-Si-Cl + H-O-R2 -> R1-Si-O-R2 + HCl, the HCl escapes as a gas and the rest stays put, covalently bonded to the surface.

Comment: Re:512 should still be too high a bar... (Score 1) 89

by jhantin (#49175927) Attached to: FREAK Attack Threatens SSL Clients

MITM positioning is a prerequisite, but that's not hard if you run a Wi-Fi hotspot. This is a bid-down attack, tampering with initial negotiation to limit the cipher suite and strength to something more breakable without raising alarms.

If you can additionally prevent the use of PFS cipher suites so the 512 bit key is used for pre-master secret encipherment, you need only break the static 512-bit key once to read all the traffic protected by it.

Comment: Re:Since when is AMT controversial? (Score 2) 179

by jhantin (#48936713) Attached to: FSF-Endorsed Libreboot X200 Laptop Comes With Intel's AMT Removed

Exactly. How is this materially different from an integrated remote-access card and baseboard management controller? I'm at a loss why Intel used an Argonaut core for it, though. I'd have expected a lightweight x86, or maybe an ARM. However, all that is beside the point.

The main reason for all the hullabaloo is that the Intel firmware that normally runs on this coprocessor is delivered as a closed-source blob, which raises trust issues given how pervasive its access to the machine is. It's also had its share of bugs and exploits, some of which work even if AMT is turned off in the BIOS, since the coprocessor may still be doing mundane baseboard tasks like fan control.

Comment: Their drivers might be garbage, the silicon's OK (Score 4, Interesting) 160

by jhantin (#48834177) Attached to: AMD Catalyst Is the Broken Wheel For Linux Gaming

AMD got the $6 billion to buy ATI by spending the cash reserves they had to build their next generation fab. The result is that after they bought ATI they had to sell their manufacturing operations sliding even further into irrelevance as their costs are much higher than Intel.

It's not like they don't actually have a sensible plan, though. While they might not be able to catch Intel in the short run on high-end CPUs, some of their newer APUs (some of them outright SoCs) are surprisingly efficient little beasts built for the low-power market segment: silent or fanless mini PCs, tablets, ultraportables, and an assortment of bespoke embedded gadgets. While the CPU side trails Intel's, on-die GCN soundly demolishes any integrated graphics Intel puts out there.

Comment: Re:Nothing has been lost! (Score 1) 290

by jhantin (#48822881) Attached to: Bitcoin Volatility Puts Miners Under Pressure

The is an infinite number that can be collected over an infinite amount of years... However at any particular point of time there is only a limited number available to be used. The the number cannot be dramatically increase or decrease with a sign of a pen.

The number of new coins issued with each block is cut in half every 210,000 blocks (approximately every four years), and summing from 1 to infinity over 1/(2**n) equals one, not infinity. The total circulation will asymptotically approach approximately 21 million.

Comment: Re: Bitcoin != Coins (Score 2) 108

by jhantin (#48713877) Attached to: Fraud, Not Hackers, Took Most of Mt. Gox's Missing Bitcoins

trading gold is nothing more than trading the energy consumed in mining it.

Gold comes from mines? I always believed it came from pawn shops and elderly relatives.

Well, the generation of that gold probably occurred in a process even more energy intensive than bitcoin mining, such as a very large star going out with a bang. After that it's just been transferred around.

Comment: Inadequate summary of Szabo's article (Score 1) 1

by jhantin (#48687885) Attached to: The Dawn of Trustworthy Computing

Nakamoto block chains don't address the problem of authenticating and authorizing transactions, they address the problem of resolving disputes over whether and when any given transaction happened. In conjunction with the block chain, digital signatures and smart contracts provide the authentication and authorization respectively, and neither technology needs access to anyone's private information when verifying or validating.

Comment: Re:More moaning and groaning for nothing. (Score 1) 206

by jhantin (#48682071) Attached to: N. Korea Blames US For Internet Outage, Compares Obama to "a Monkey"

It doesn't stop at 'name endianness'. It's probably less confusing, in print at least, to use the convention of all-capping the surname while leaving the full name in its native order. I imagine such a convention would be especially handy when trying to wrangle elaborate names carrying a whole syntax tree laden with titles, adjective phrases, and prepositional phrases, leaving the surname somewhere in the middle. Such names tend to be found in Europe and the Middle East at least.

The downside to smashing case is that it loses information, such as whether 'VON FOO' is properly cased as 'von Foo' or 'Von Foo'. Where possible it's probably better to use an inline tag or something, but plain text doesn't leave room for such niceties.

This file will self-destruct in five minutes.