Commit 73dc7071 authored by Guoqing Jiang's avatar Guoqing Jiang Committed by Theodore Ts'o

ext4: remove conflicting comment from __ext4_forget

We do a bforget and return for no journal case, so let's remove this
conflict comment.
Reviewed-by: default avatarJan Kara <jack@suse.cz>
Signed-off-by: default avatarGuoqing Jiang <jiangguoqing@kylinos.cn>
Link: https://lore.kernel.org/r/20210714055940.1553705-1-guoqing.jiang@linux.devSigned-off-by: default avatarTheodore Ts'o <tytso@mit.edu>
parent b6654142
...@@ -244,9 +244,6 @@ int __ext4_journal_get_write_access(const char *where, unsigned int line, ...@@ -244,9 +244,6 @@ int __ext4_journal_get_write_access(const char *where, unsigned int line,
* "bh" may be NULL: a metadata block may have been freed from memory * "bh" may be NULL: a metadata block may have been freed from memory
* but there may still be a record of it in the journal, and that record * but there may still be a record of it in the journal, and that record
* still needs to be revoked. * still needs to be revoked.
*
* If the handle isn't valid we're not journaling, but we still need to
* call into ext4_journal_revoke() to put the buffer head.
*/ */
int __ext4_forget(const char *where, unsigned int line, handle_t *handle, int __ext4_forget(const char *where, unsigned int line, handle_t *handle,
int is_metadata, struct inode *inode, int is_metadata, struct inode *inode,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment