linux-kernel - Re: [mm PATCH 6/6] RCU: trivial fixes

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 16 Jan 2007 01:01:03 +0530
From:	Dipankar Sarma <dipankar@...ibm.com>
To:	Andrew Morton <akpm@...l.org>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Paul E McKenney <paulmck@...ux.vnet.ibm.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [mm PATCH 6/6] RCU: trivial fixes


Fix a few trivial things based on review comments.

Signed-off-by: Dipankar Sarma <dipankar@...ibm.com>

---



diff -puN kernel/rcupreempt.c~rcu-fix-trivials kernel/rcupreempt.c
--- linux-2.6.20-rc3-mm1-rcu/kernel/rcupreempt.c~rcu-fix-trivials	2007-01-15 15:37:00.000000000 +0530
+++ linux-2.6.20-rc3-mm1-rcu-dipankar/kernel/rcupreempt.c	2007-01-15 15:37:00.000000000 +0530
@@ -156,7 +156,7 @@ void __rcu_read_lock(void)
 		local_irq_save(oldirq);
 
 		/*
-		 * Outermost nesting of rcu_read_lock(), so atomically
+		 * Outermost nesting of rcu_read_lock(), so 
 		 * increment the current counter for the current CPU.
 		 */
 		idx = rcu_ctrlblk.completed & 0x1;
@@ -169,7 +169,7 @@ void __rcu_read_lock(void)
 		 * Now that the per-CPU counter has been incremented, we
 		 * are protected.  We can therefore safely increment
 		 * the nesting counter, relieving further NMIs of the
-		 * need to do so.
+		 * need to increment the per-CPU counter.
 		 */
 		current->rcu_read_lock_nesting = nesting + 1;
 		barrier();

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