Re: [f2fs-dev] [PATCH 1/1] f2fs: fix to check space of current segment journal

2022-09-19 Thread Jaegeuk Kim
Hi Philippe, Kernel 4.1 is really old one, so is there any chance to upgrade the kernel at least 4.14? You can find all the backports from below. https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-stable.git On 09/16, Philippe De Muyter wrote: > Tnank you for your patch. > > I have

Re: [f2fs-dev] [PATCH 1/1] f2fs: fix to check space of current segment journal

2022-09-16 Thread Philippe De Muyter
Tnank you for your patch. I have applied it and also applied f2fs patches from 4.1.54 to my driver which was in the 4.1.5 state, but I still get sometimes [ cut here ] WARNING: CPU: 0 PID: 2333 at fs/f2fs/node.c:1863 flush_nat_entries+0x74c/0x7d8() Modules linked in:

Re: [f2fs-dev] [PATCH 1/1] f2fs: fix to check space of current segment journal

2022-09-15 Thread Wu Bo via Linux-f2fs-devel
On 2022/9/14 16:08, Philippe De Muyter wrote: > Hello Wu Bo, > > On Wed, Sep 14, 2022 at 12:04:23PM +0800, Wu Bo wrote: >> As Philippe De Muyter reported: >> https://lore.kernel.org/linux-f2fs-devel/20220913224908.GA25100@172.21.0.10/T/#u >> >> The warning log showed that when finding a new space

Re: [f2fs-dev] [PATCH 1/1] f2fs: fix to check space of current segment journal

2022-09-14 Thread Philippe De Muyter
Hello Wu Bo, On Wed, Sep 14, 2022 at 12:04:23PM +0800, Wu Bo wrote: > As Philippe De Muyter reported: > https://lore.kernel.org/linux-f2fs-devel/20220913224908.GA25100@172.21.0.10/T/#u > > The warning log showed that when finding a new space for nat the journal > space turned out to be full.