Re: [PATCH] f2fs: fix a deadlock in fsync

Hi Jin, 2013-08-07 (수), 12:23 +0800, Jim Xu: > Hi Kim, > > The patch sounds good to me. > > BTW, as in the deadlock situation I noticed, I did not find any thread was > doing checkpoint at that moment. The bdi writeback thread and the fsync user > thread was not. Neither was the background f2f

Re: [PATCH] f2fs: fix a deadlock in fsync

to the > update_inode. And, I can clean up another minor flow too. > > Please check the below patch. > Thanks, > > > > > From a9c62162ea89c9b6b52d39d6db3f8f27c4d2ce5c Mon Sep 17 00:00:00 2001 > From: Jin Xu > Date: Mon, 5 Aug 2013 20:02:04 +0800 > Subject:

Re: [PATCH] f2fs: fix a deadlock in fsync

, __set_data_blkaddr, in addition to the update_inode. And, I can clean up another minor flow too. Please check the below patch. Thanks, > >From a9c62162ea89c9b6b52d39d6db3f8f27c4d2ce5c Mon Sep 17 00:00:00 2001 From: Jin Xu Date: Mon, 5 Aug 2013 20:02:04 +0800 Subject: [PATCH] f2fs: fix a deadlock in

[PATCH] f2fs: fix a deadlock in fsync

From: Jin Xu This patch fixes a deadlock bug that occurs quite often when there are concurrent write and fsync on a same file. Following is the simplified call trace when tasks get hung. fsync thread: - f2fs_sync_file ... - f2fs_write_data_pages ... - update_extent_cache ... - update_