Hi Andrew,
Please add the following patches to the queue for the next merge
window.
Andreas's one simplifies nilfs_sync_file() function to avoid duplicate
segment construction on fsync(), and mine fixes a race issue between
nilfs_iget() and nilfs_new_inode(). Markus's one removes an
unnecessary
From: Markus Elfring elfr...@users.sourceforge.net
The iput() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
same story as in commit 41080b5a240113328c607f22b849f653373db0ce
(similar ext2 fix) except that nilfs2 needs to use
insert_inode_locked4() instead of insert_inode_locked() and a bug of a
check for dead inodes needs to be fixed.
If nilfs_iget() is called from nfsd after nilfs_new_inode() calls
Andreas,
On Sun, 9 Nov 2014 17:00:12 +0100, Andreas Rohner wrote:
This patch removes filemap_write_and_wait_range() from
nilfs_sync_file(), because it triggers a data segment construction by
calling nilfs_writepages() with WB_SYNC_ALL. A data segment construction
does not remove the inode
On 2014-12-01 18:13, Ryusuke Konishi wrote:
Andreas,
On Sun, 9 Nov 2014 17:00:12 +0100, Andreas Rohner wrote:
This patch removes filemap_write_and_wait_range() from
nilfs_sync_file(), because it triggers a data segment construction by
calling nilfs_writepages() with WB_SYNC_ALL. A data
On Tue, 2 Dec 2014 01:41:45 +0900, Ryusuke Konishi wrote:
From: Andreas Rohner andreas.roh...@gmx.net
This patch removes filemap_write_and_wait_range() from
nilfs_sync_file(), because it triggers a data segment construction by
calling nilfs_writepages() with WB_SYNC_ALL. A data segment
