linux-kernel - [PATCH] buffer_read_full

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: <1338808614-4261-1-git-send-email-liwp.linux@gmail.com>
Date:	Mon,  4 Jun 2012 19:16:54 +0800
From:	Wanpeng Li <liwp.linux@...il.com>
To:	Alexander Viro <viro@...iv.linux.org.uk>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:	Wanpeng Li <liwp.linux@...il.com>,
	Wanpeng Li <liwp@...ux.vnet.ibm.com>
Subject: [PATCH] buffer_read_full_page:make comments tidy

From: Wanpeng Li <liwp@...ux.vnet.ibm.com>

Since the function has already have comments "Stage two: xxx" and "Stage
3: xxx", so add "Stage one: xxx" in order to make comments tidy.

Signed-off-by: Wanpeng Li <liwp@...ux.vnet.ibm.com>
---
 fs/buffer.c |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/fs/buffer.c b/fs/buffer.c
index ad5938c..e49b6a1 100644
--- a/fs/buffer.c
+++ b/fs/buffer.c
@@ -2086,6 +2086,7 @@ int block_read_full_page(struct page *page, get_block_t *get_block)
 	nr = 0;
 	i = 0;
 
+	/* Stage one: find the buffers */
 	do {
 		if (buffer_uptodate(bh))
 			continue;
@@ -2138,7 +2139,7 @@ int block_read_full_page(struct page *page, get_block_t *get_block)
 	}
 
 	/*
-	 * Stage 3: start the IO.  Check for uptodateness
+	 * Stage three: start the IO.  Check for uptodateness
 	 * inside the buffer lock in case another process reading
 	 * the underlying blockdev brought it uptodate (the sct fix).
 	 */
-- 
1.7.9.5

--
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/