On Tue, Oct 28, 2014 at 03:29:10PM +0100, Johan Hovold wrote: > Hi, > > I have had some problems with crashes involving suspend-to-disk after > updating to v3.16. > > Below is a log with 3.16.6 from a failed suspend attempt after which I > get a NULL deref in ext4 code. > > A couple of weeks ago I got something similar, with backtraces from > ext4 (ext4_alloc_inode) and NULL-derefs in vfs (vfs_get_attr_nosec) when > trying to do IO after resuming from suspend. That was with 3.16.3 and I > was hoping that whatever it was would have been fixed in 3.16.6 (there > were some ext4 error handling patches in there). I only got photos of > those oopses but it involved kmem_cache_alloc (slub) and a NULL-deref in > vfs_get_attr_nosec. I can put the photos up somewhere. That time I also > got back to X and could issue a dmesg in an xterm, but any process trying > to do IO died. > > Something similar happened with 3.16.1 but unfortunately I do not have > any logs from that. For the record, it seems this problem went away with 3.17 (.2 and .3). Been suspending daily now for almost three weeks without triggering this again. Since 3.16 is EOL (and 3.15 did not suffer from this) I guess there's no need to track it down for stable. Johan -- 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
