linux-kernel - [PATCH 1/1 linux-next] ext4: fix comment in evict

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <1407140787-3742-1-git-send-email-fabf@skynet.be>
Date:	Mon,  4 Aug 2014 10:26:26 +0200
From:	Fabian Frederick <fabf@...net.be>
To:	linux-kernel@...r.kernel.org
Cc:	Fabian Frederick <fabf@...net.be>, "Theodore Ts'o" <tytso@....edu>,
	Andreas Dilger <adilger.kernel@...ger.ca>,
	linux-ext4@...r.kernel.org
Subject: [PATCH 1/1 linux-next] ext4: fix comment in evict_inode()

commit 91b0abe36a7b
("mm + fs: store shadow entries in page cache")

replaced truncate_inode_pages by truncate_inode_pages_final

Signed-off-by: Fabian Frederick <fabf@...net.be>
---
 fs/ext4/inode.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
index 367a60c..16d429f 100644
--- a/fs/ext4/inode.c
+++ b/fs/ext4/inode.c
@@ -197,8 +197,8 @@ void ext4_evict_inode(struct inode *inode)
 		 * ready for reaping the inode might still have some pages to
 		 * write in the running transaction or waiting to be
 		 * checkpointed. Thus calling jbd2_journal_invalidatepage()
-		 * (via truncate_inode_pages()) to discard these buffers can
-		 * cause data loss. Also even if we did not discard these
+		 * (via truncate_inode_pages_final()) to discard these buffers
+		 * can cause data loss. Also even if we did not discard these
 		 * buffers, we would have no way to find them after the inode
 		 * is reaped and thus user could see stale data if he tries to
 		 * read them before the transaction is checkpointed. So be
-- 
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/