On Fri, Aug 08, 2014 at 05:17:54PM -0700, John Stultz wrote: > On 08/08/2014 05:15 PM, Kees Cook wrote: > > On Fri, Aug 8, 2014 at 2:14 PM, John Stultz <[email protected]> wrote: > >> I sunk a couple of weeks bisecting to try to narrow down the more > >> sporadic issue, but was unsuccessful past the initial commit above. > >> Since then I've been far too swamped to spend any more time on it. Even > >> so, its a *major* pain for testing but it seems like no one else really > >> cares? > > I'm in the same boat as far as poor bisection results. :( > > > > However, I keep using the 3-patch mmci fix series from Ulf, and > > haven't hit any trouble with them. Though perhaps I'm just getting > > lucky? > > > > http://git.kernel.org/cgit/linux/kernel/git/kees/linux.git/log/?h=arm/fix-mmci > > I guess I'll give that another shot
There was an ext4 bug that might have caused this problem. It was fixed in v3.15.6 and v3.16-rc5. commit f9ae9cf5d72b3926ca48ea60e15bdbb840f42372 Author: Theodore Ts'o <[email protected]> Date: Fri Jul 11 13:55:40 2014 -0400 ext4: revert commit which was causing fs corruption after journal replays Commit 007649375f6af2 ("ext4: initialize multi-block allocator before checking block descriptors") causes the block group descriptor's count of the number of free blocks to become inconsistent with the number of free blocks in the allocation bitmap. This is a harmless form of fs corruption, but it causes the kernel to potentially remount the file system read-only, or to panic, depending on the file systems's error behavior. Thanks to Eric Whitney for his tireless work to reproduce and to find the guilty commit. Fixes: 007649375f6af2 ("ext4: initialize multi-block allocator before checki Cc: [email protected] # 3.15 Reported-by: David Jander <[email protected]> Reported-by: Matteo Croce <[email protected]> Tested-by: Eric Whitney <[email protected]> Suggested-by: Eric Whitney <[email protected]> Signed-off-by: Theodore Ts'o <[email protected]> The bug wouldn't always trigger, which is probably why it gave you so much trouble trying to do the bisect. Cheers, - Ted -- 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/
