linux-kernel - Re: [PATCH-v2 0/4] target: Eliminate se_port + t10_alua_tg_pt_gp

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]

Message-ID: <55646A9E.5050401@sandisk.com>
Date:	Tue, 26 May 2015 14:44:14 +0200
From:	Bart Van Assche <bart.vanassche@...disk.com>
To:	"Nicholas A. Bellinger" <nab@...erainc.com>,
	target-devel <target-devel@...r.kernel.org>
CC:	linux-scsi <linux-scsi@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Christoph Hellwig <hch@....de>,
	"Hannes Reinecke" <hare@...e.de>,
	Sagi Grimberg <sagig@...lanox.com>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Nicholas Bellinger <nab@...ux-iscsi.org>
Subject: Re: [PATCH-v2 0/4] target: Eliminate se_port + t10_alua_tg_pt_gp_member

On 05/26/15 08:57, Nicholas A. Bellinger wrote:
>    - Add various rcu_dereference and lockless_dereference RCU notation

Hello Nic,

Feedback from an RCU expert (which I'm not) would be appreciated here. 
But my understanding is that lockless_dereference(p) should be used for 
a pointer p that has *not* been annotated as an RCU pointer. I think in 
the for-next branch of the target repository that this macro is used to 
access RCU-annotated pointers. Is that why sparse complains about how 
lockless_dereference() is used in the target tree ?

Bart.

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