Neil Bothwick wrote: > On Thu, 25 Oct 2012 15:10:17 -0500, Dale wrote: > >> Or just don't update the kernel until it is fixed. After all, if the >> kernel you are using works and is not a serious security problem, just >> use it for a while. They will fix it pretty soon I'm sure. > Several versions are affected, it's not a new issue, just a newly > discovered one. That in itself indicates the likelihood of being affected > by it, considering how many boxes use ext4 with these kernel versions. > >
My point is, if you are using a version that is not affected, keep using it, don't upgrade yet. I saw a list of the affected versions. Just avoid those for now. Is it a perfect plan, of course not. It's better than nothing tho. It's certainly better than using a known version with this problem. If a person is using an affected version, then I would reboot to another kernel that is not on the list. Now if someone wants to keep using a known version that is affected, that's their thing. Since I don't reboot much, it would likely not affect me either way. Thing is, I'm not going to take the chance either way. That is of course if the problem is what I read and not something else all together. The problem seems to be a moving target since it is not exactly known yet. Either way, having the information is better than nothing. Avoiding the affected versions is better than nothing. None of this may matter depending on all sorts of things. Me, I'm going to stick with what I am using, that's not on the affected list so far, and wait until whatever version has a known fix. That's my plan for now, subject to change if the situation changes. Oh, going to cross fingers too. ;-) Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
