Skip to content

Commit

Permalink
---
Browse files Browse the repository at this point in the history
yaml
---
r: 108543
b: refs/heads/master
c: 7d62ff2
h: refs/heads/master
i:
  108541: e7f231c
  108539: 7f8f9fd
  108535: 38625f3
  108527: 33824ce
  108511: e87772a
  108479: 444207d
  108415: 1d69375
  108287: 047cb3e
  108031: 9592a77
  107519: 6a6a436
  106495: 875b556
v: v3
  • Loading branch information
Adrian Hunter authored and Artem Bityutskiy committed Aug 13, 2008
1 parent 7a17995 commit b556ed9
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion [refs]
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
---
refs/heads/master: bc813355c704e5916a86dd4b96fd226bfa3fc6ca
refs/heads/master: 7d62ff2c396470bb62a3853f14d3962eac1da974
10 changes: 5 additions & 5 deletions trunk/fs/ubifs/journal.c
Original file line number Diff line number Diff line change
Expand Up @@ -822,7 +822,7 @@ int ubifs_jnl_write_inode(struct ubifs_info *c, const struct inode *inode)
}

/**
* ubifs_jnl_write_inode - delete an inode.
* ubifs_jnl_delete_inode - delete an inode.
* @c: UBIFS file-system description object
* @inode: inode to delete
*
Expand All @@ -831,21 +831,21 @@ int ubifs_jnl_write_inode(struct ubifs_info *c, const struct inode *inode)
* journal.
*
* When regular file inodes are unlinked or a directory inode is removed, the
* 'ubifs_jnl_update()' function write corresponding deletion inode and
* 'ubifs_jnl_update()' function writes a corresponding deletion inode and
* direntry to the media, and adds the inode to orphans. After this, when the
* last reference to this inode has been dropped, this function is called. In
* general, it has to write one more deletion inode to the media, because if
* a commit happened between 'ubifs_jnl_update()' and
* 'ubifs_jnl_delete_inode()', the deletion inode is not in the journal
* anymore, and in fact it might be not on the flash anymore, becouse it might
* have been garbage-collected already. And for optimization reasond UBIFS does
* anymore, and in fact it might not be on the flash anymore, because it might
* have been garbage-collected already. And for optimization reasons UBIFS does
* not read the orphan area if it has been unmounted cleanly, so it would have
* no indication in the journal that there is a deleted inode which has to be
* removed from TNC.
*
* However, if there was no commit between 'ubifs_jnl_update()' and
* 'ubifs_jnl_delete_inode()', then there is no need to write the deletion
* inode to the media for the second time. And this is quite typical case.
* inode to the media for the second time. And this is quite a typical case.
*
* This function returns zero in case of success and a negative error code in
* case of failure.
Expand Down

0 comments on commit b556ed9

Please sign in to comment.