1 |
Am Donnerstag, 25. Oktober 2012, 22:04:12 schrieb Kerin Millar: |
2 |
> Grant Edwards wrote: |
3 |
> > On 2012-10-25, Kerin Millar<kerframil@×××××××××××.uk> wrote: |
4 |
> >> The comment you linked to was fairly bereft of technical content, |
5 |
> > |
6 |
> > That "comment" was from _Ted_Ts'o_ for pete's sake. |
7 |
> |
8 |
> I don't care it was from the heavens upon high. The only remark that was |
9 |
> meaningful in a technical sense was the thoroughly inconclusive |
10 |
> "Update", suggesting (but not establishing) that it might be related to |
11 |
> certain combinations of mount options. The rest was just hand-waving |
12 |
> about how it couldn't be a big deal because, if it was, "lots of people |
13 |
> would have been complaining", which is denying the antecedent. |
14 |
> |
15 |
> Let's separate two fundamental issues here. One issue is that of data |
16 |
> corruption, which is a big deal. I'm sure most of us would agree on that |
17 |
> point. That such an issue is going to generate news - and no small |
18 |
> degree of discussion - is a given. People will want to know what the |
19 |
> problem is and what they can do about it in order to be safe. What did |
20 |
> Ted expect? |
21 |
> |
22 |
> The second issue is that of the scope of the bug. This is where I took |
23 |
> issue with the comment. The overall meaning of his comment could be |
24 |
> interpreted as "Your collective concerns are overblown because the scope |
25 |
> of this bug is minimal. Oh, and I think it may have something to do with |
26 |
> these mount options which, being esoteric, nobody in their right mind |
27 |
> would be using anyway so, hey, big deal." |
28 |
> |
29 |
> The fact of the matter is that the investigation, even as I write this, |
30 |
> is ongoing and no patch has been produced. Consider that for a moment. |
31 |
> It doesn't matter how brilliant Ted is, or that you have seen fit to |
32 |
> sample his mucus. Telling us all that we should be unconcerned because |
33 |
> the scope is minimal *before* he and his peers have completed their |
34 |
> investigation and a line been drawn under the affair was simply premature. |
35 |
> |
36 |
> That the bug reporter has since demonstrated that the corruption can |
37 |
> occur in kernel versions that don't include commit eeecef0af5 - kernels |
38 |
> which we were previously told were not affected - only serves to |
39 |
> demonstrate this point. |
40 |
> |
41 |
|
42 |
and that ONLY two people who did some REALLY stupid stuff to stumble over that |
43 |
bug are hit by it, should tell you something. For fucks sake, if you had read |
44 |
the thread, even google uses ext4 and they did not hit it. So much about its |
45 |
likelyhood. |
46 |
|
47 |
Bugs happen. And this bug is so not a problem. |
48 |
|
49 |
-- |
50 |
#163933 |