Please create an account to participate in the Slashdot moderation system


Forgot your password?

Comment Re:awkward! (Score 1) 183

I'm aware of the company that found the actual problem - I specifically stated that I read the linked articles, and that link you provided is one of the ones already linked. Obviously the kernel devs erred when they automatically assumed there wasn't a kernel bug.

That said, Linus never apologises for his own out-rightly abusive comments and actions. There's no way he's going to apologise on behalf of someone else, especially when there's some truth to the kernel developers comments - there are known bugs in the Samsung firmware. They just made the mistake of assuming that this particular one was one of those instead of one of their own. The best we can hope for is those responsible developers apologising on their own behalf.

Comment Re:Just another case.... (Score 1) 183

This is just another case of "Not My Problem" syndrome that too many techs get into.

No, it's a case of everyone jumping to conclusions.

Samsung drives went on a blacklist for issuing the commands to them due to this bug?

No, they went on the queued TRIM blacklist due to a different bug. This bug was an unrelated serial TRIM bug when used in conjunction with RAID.

Comment Re:Crying wolf (Score 4, Informative) 183

That really depends on whether OS X uses serial or queued TRIM. The Samsung drives work fine with serial TRIM, but are still broken with queued TRIM. The bug that Algolia reported and Samsung fixed in the kernel was a serial TRIM issue in the Linux kernel with RAID, which is unrelated to the queued TRIM firmware issues.

Comment Re:awkward! (Score 3, Informative) 183

The queued TRIM blacklist on Samsung drives doesn't affect Windows because Windows doesn't support queued TRIM yet. This Linux kernel bug is a different issue, but many assumed it was the same, even though Algolia clearly stated in their blog post that they weren't using queued TRIM.

Comment Re:awkward! (Score 5, Informative) 183

I've read the articles. There are two separate bugs here. One, Samsung drives advertise support for queued TRIM even though it's not properly supported, causing corruption. Two, the kernel had a TRIM bug that affected serial TRIM with mdadm RAID, which is the kernel bug Samsung found and fixed. The queued TRIM bug still exists in the Samsung firmware.

Where are the calculations that go with a calculated risk?