First, yes it is caused by data_flush, this is what I am trying to report. Without that option there is no "stack guard page was hit" and no "kernel stack overflow" and kernel is stable. This time I was using kernel 5.0.3, as can be seen in the log in my first mail. I do not remember exactly what kernel version I tried the first time a saw this bug, but I believe the mount option data_flush was just added when I tried it the first time. The option has always lead to crash here.
2019-03-30 8:29 GMT+01:00, Chao Yu <yuch...@huawei.com>: > Oh, sorry, it's quite possible that bug is caused by data_flush, could > remove that mount option first? > > Thanks, > > On 2019/3/30 11:25, Chao Yu wrote: >> Hi Hagbard, >> >> Sorry for the delay. >> >> On 2019/3/27 21:59, Hagbard Celine wrote: >>> Hi, this is a long standing bug that I've hit before on older kernels, >>> but I was not able to get the syslog saved because of the nature of >>> the bug. This time I had booted form a pen-drive, and was able to save >>> the log to it's efi-partition. >> >> Now which version of kernel do you use? and do you remember what is your >> kernel version when this bug occured at first time? >> _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
