On Tuesday, 26 of February 2008, Eric Sandeen wrote: > Rafael J. Wysocki wrote: > > On Monday, 25 of February 2008, Eric Sandeen wrote: > > > >> If you're feeling motivated, maybe you can narrow it down to which of > >> the changes - xfs_highbit32, xfs_highbit64, xfs_lowbit32, or > >> xfs_lowbit64 - is causing the problem? (or maybe they all are ...) > >> > >> Or maybe someone looking at the commit can immediately see the > >> problem... but I can't :) > > > > Well, IMO a reproducible filesystem corruption is a serious enough issue > > for reverting all of the commits in question. > > I'm not suggesting a partial revert; I just wonder which part of the > change is causing the problem, as part of the debugging process.
Understood. My point is, if that's not practical (whatever the reason), I'd consider reverting all of the commits in question. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
