On Thu, May 14, 2015 at 10:37:21AM +1000, Dave Chinner wrote:
> On Tue, May 12, 2015 at 11:48:02PM -0700, Jaegeuk Kim wrote:
> > On Wed, May 13, 2015 at 12:02:08PM +1000, Dave Chinner wrote:
> > > On Fri, May 08, 2015 at 09:20:38PM -0700, Jaegeuk Kim wrote:
> > > > This definitions will be used by
I'll push the patch into dev branch right now.
Let me know, if there is any problem.
Thanks,
On Thu, May 14, 2015 at 09:40:25AM +0800, hujianyang wrote:
> Hi Jaegeuk,
>
> I've tested this patch. It's OK now. Seems this problem is fixed.
>
> I'd like to push this patch to my local tree and run a
Hi Jaegeuk,
I've tested this patch. It's OK now. Seems this problem is fixed.
I'd like to push this patch to my local tree and run a formal
stress test next week. Will you push this patch to f2fs-dev branch?
If you have other modification to this fix, please let me know.
Thanks very much!
Hu
O
On Tue, May 12, 2015 at 11:48:02PM -0700, Jaegeuk Kim wrote:
> On Wed, May 13, 2015 at 12:02:08PM +1000, Dave Chinner wrote:
> > On Fri, May 08, 2015 at 09:20:38PM -0700, Jaegeuk Kim wrote:
> > > This definitions will be used by inode and superblock for encyption.
> >
> > How much of this crypto s
Hi Hu,
Found a bug in the previous patch.
Could you check this out?
Thanks,
---
fs/f2fs/super.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
index 19438f2..647591b 100644
--- a/fs/f2fs/super.c
+++ b/fs/f2fs/super.c
@@ -431,8 +
Hi Arnd,
Thank you for the patch.
Merged and pushed to -next. :)
Thanks,
On Wed, May 13, 2015 at 10:49:58PM +0200, Arnd Bergmann wrote:
> A bug fix to the debug output extended the type of some local
> variables to 64-bit, which now causes the kernel to fail building
> because of missing 64-bit
A bug fix to the debug output extended the type of some local
variables to 64-bit, which now causes the kernel to fail building
because of missing 64-bit division functions:
ERROR: "__aeabi_uldivmod" [fs/f2fs/f2fs.ko] undefined!
In the kernel, we have to use div_u64 or do_div to do this,
in order
Hi Hu,
Thank you for the report.
When I tried to reproduce this, it seems that this can occur under somewhat
stressful condition. I could't reach out to this problem.
Nevertheless, I think this is a possible scenario, so I wrote a patch for this.
Could you test this patch?
Thanks,
---
fs/f2fs
This patch fixes memory leak issue in error path of f2fs_fname_setup_filename().
Signed-off-by: Chao Yu
---
fs/f2fs/crypto_fname.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/fs/f2fs/crypto_fname.c b/fs/f2fs/crypto_fname.c
index e3a1bdc..016c4b6 100644
--- a/fs
Hi Jaegeuk,
I found a space leak problem in f2fs. This problem could lead to
ENOSPC error during stress tests, e.g. ltp.
<<>>
growfiles(gf15): 11656 growfiles.c/2249: 16920 tlibio.c/739 write(6, buf, 1352)
ret:-1, errno=28 No space left on device
gf151 TFAIL : growfiles.c:132: Test fa
10 matches
Mail list logo