On Mon 02-05-11 14:29:45, Ted Tso wrote: > On Mon, May 02, 2011 at 05:07:58PM +0200, Jan Kara wrote: > > The patch looks OK in any case. I'll take it in my tree. > Great, thanks. > > > It would take > > about 24 days of constant 1000 trans/s load to trigger this. That's a quite > > heavy load but not so unrealistic with today's HW. > > True; but one of the reason why I'm not sure I believe that is this > bug is showing up on some Android devices, where (a) 1000 trans/second > *is* a not just a huge load, but almost impossible to believe, and (b) > if we really are doing 2**31 commits, we would be wearing out the > flash storage being used on the Android devices! (And we're seeing a > handful of failures every week from the testers who participate in a > kerneloops-like reporting system.) Ah, OK. I didn't know it's so many reports. Indeed it looks like there's another bug. But then the WARN you have added should tell us more about who's causing the problem, right? Honza -- Jan Kara <jack@xxxxxxx> SUSE Labs, CR -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
