Hi Marcelo,
On 2017/10/13 12:19, Marcelo "Marc" Ranolfi wrote:
> Hello Chao,
>
> I was holding for a while and taking care of other things, but now
> since I upgraded to kernel v4.13 (in fact I jumped to 4.13.3), I seem
> to be no longer affected by this problem.
>
> My system has been running
Hello Chao,
I was holding for a while and taking care of other things, but now
since I upgraded to kernel v4.13 (in fact I jumped to 4.13.3), I seem
to be no longer affected by this problem.
My system has been running fine for over two weeks.
I appreciate your help in this matter. Should I
Hi,
no problem at all.
No, I never did ro remount before it happened. In fact its been a long
while since I used ro.
Regards
On Thu, Aug 31, 2017 at 8:01 AM, Chao Yu wrote:
> Hi Marcelo,
>
> Sorry for the delay, :(
>
> I'd like ask, any possible that we did ro remount
Hi Marcelo,
Sorry for the delay, :(
I'd like ask, any possible that we did ro remount before the problem happened?
Thanks,
On 2017/8/24 1:26, Marcelo "Marc" Ranolfi wrote:
> Chao,
>
> I just had the same problem, with kernel 4.12.8 with patch _f2fs: fix
> out-of-order execution in
Hi,
as an update, I've been able to reproduce this bug reliably by using a
lot of RAM in order to force swap (I have vm_swappiness at 10).
Once swapping takes place, it's only a matter of time until some
userspace application locks at f2fs_issue_flush.
It will remain locked even when I free
Chao,
I just had the same problem, with kernel 4.12.8 with patch _f2fs: fix
out-of-order execution in f2fs_issue_flush_.
On Tue, Aug 22, 2017 at 2:00 PM, Marcelo "Marc" Ranolfi
wrote:
> Hi Chao
>
> I'm testing the kernel with your patch since last night. Will give new
>
Hi Chao
I'm testing the kernel with your patch since last night. Will give new
feedback a couple of days/weeks about how it goes.
Thank you.
On Mon, Aug 21, 2017 at 11:58 AM, Chao Yu wrote:
> Hi Marcelo,
>
> Thanks for the report!
>
> Would you have a try with below patch?
Hi Marcelo,
Thanks for the report!
Would you have a try with below patch?
f2fs: fix out-of-order execution in f2fs_issue_flush
Thanks,
On 2017/8/16 15:24, Marcelo "Marc" Ranolfi wrote:
> Just wanted to let you all know that this is still an issue, even with
> the 4.12.7 kernel.
>
> The two
Just wanted to let you all know that this is still an issue, even with
the 4.12.7 kernel.
The two most affected applications are qemu-system-x86_64 and totem.
On Wed, Aug 9, 2017 at 3:04 AM, Marcelo "Marc" Ranolfi
wrote:
> What follows is a bug report.
>
> I've been