From: Boaz H. <bha...@pa...> - 2010-09-12 09:48:48
|
On 09/12/2010 09:34 AM, Sakari Ailus wrote: >> - Please send a detailed bug report about that data corruption so someone >> can reproduce it. I'm not sure what block device you are using but it has >> a bug. If you have a good version 2.6.27 and a bad version 2.6.28. It should >> be easy to "git bisect" to the exact patch that broke the system, and should >> be easy to fix. (Tell me if you need help, it's easy really) > > I did write about this back then but it seems no-one else had the same > problem. It's one thing to find it and the other to fix it. My wild > guess is that it's not a change to that actual driver that broke it. > A "git bisect" should be the best way to find what exactly broke it. If it's not the driver then fine, that will be found as well. Can you reliably reproduce the data corruption? If yes then a git bisect should be easy. Please try to see what you can do? Thanks Boaz |