On 09/21/2010 05:35 PM, Miles Fidelman wrote:
Tim Small wrote:
tim@zebedee:~$ zgrep -i raid
/usr/share/doc/linux-image-2.6.26-2-amd64/changelog.Debian.gz | egrep
-v '(aacraid|megaraid|cpq|5c1|dm|DM|cciss|LVM|sym)'
- md: handle writes to broken raid10 arrays gracefully
- md: raid10: fix use-after-free of bio
- md: Fix raid10 recovery problem.
- md: Avoid oops when attempting to fix read errors on raid10
Uh oh. Now I am worried. I've been running 2.6.26-2-xen-686, on a couple
of production machines, for a while now, on top of RAID10 - and that
version of the kernel doesn't get a lot of attention.
Sigh...
I wouln't worry about it, this is mostly churn, they add some, break
some, fix some. The kernel that distributions release have been
stabilized and 'frozen' for a good while meaning they are usually pretty
safe, even if they can seem quite old. I'm also willing to bet that
those fixes are mostly for corner cases rarely seen in the wild.
If you had been watching the linux-kernel list you'd be surprised your
machines boot at all. ;)
Don't worry, be happy (until it blows up.)
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
