1 |
On Sat, Oct 27, 2012 at 12:16 PM, Volker Armin Hemmann |
2 |
<volkerarmin@××××××××××.com> wrote: |
3 |
> Am Freitag, 26. Oktober 2012, 01:34:35 schrieb Neil Bothwick: |
4 |
>> On Thu, 25 Oct 2012 15:10:17 -0500, Dale wrote: |
5 |
>> > Or just don't update the kernel until it is fixed. After all, if the |
6 |
>> > kernel you are using works and is not a serious security problem, just |
7 |
>> > use it for a while. They will fix it pretty soon I'm sure. |
8 |
>> |
9 |
>> Several versions are affected, it's not a new issue, just a newly |
10 |
>> discovered one. That in itself indicates the likelihood of being affected |
11 |
>> by it, considering how many boxes use ext4 with these kernel versions. |
12 |
> |
13 |
> since only two persons ever hit it, it is a pretty save bet that this bug is |
14 |
> so uncommon that you should not waste any sleep over it. |
15 |
> |
16 |
> -- |
17 |
> #163933 |
18 |
> |
19 |
|
20 |
For fear of leading anyone down a path that eventually causes them |
21 |
problems I won't attempt to communicate the root cause or fixes but |
22 |
there is new information, and a potential patch verified by the only |
23 |
person to see this problem, about what causes the corruption. Read the |
24 |
thread if this makes any difference in your life. Don't worry about it |
25 |
if it doesn't. |
26 |
|
27 |
Basically, it's apparently driven by mount options and something the |
28 |
OP (of the lkml thread) did which most users are unlikely IMO to ever |
29 |
try. |
30 |
|
31 |
- Mark |