On Mon, Apr 25, 2016 at 09:46:19AM +0800, Barry Kauler wrote: > I sent this direct to Greg KH yesterday morning. 24 hours later got an > automated reply to send my email to one of the lists. > > I'm a user, not a kernel developer, gotta post this somewhere. > > I reckon this is urgent. > I have rolled back from 4.4.8 to 4.4.7, have used heavily for 24 hours > since then, > no problem. So, it's the kernel, not my laptop. No one else has reported any problems to date, and there are only two changes in ext4 code between v4.4.7 and v4.4.8, neither of which seem at all likely to cause file system corruption. ee8516a ext4: ignore quota mount options if the quota feature is enabled 321299a ext4: add lockdep annotations for i_data_sem If you can send us the "EXT4-fs error" message that would have been logged before the file system went read-only, or the output from e2fsck, that might be helpful in matching up your report from any others, or to have some insight into what might have happened. Unfortunately, without any more information there's not much we can do with your report other than to keep an ear out in case anyone else complains. Thanks, - Ted -- 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
