On Thu, Jun 22, 2017 at 10:48:46AM -0700, James Smart wrote: > He can't move it. the fcport->nvme_remote_port pointer is set by the > nvme_fc_register_remoteport() routine (if return status is 0). Gah, that's kind of wired. Literly _all_ of the Kernel's register_xxx() funtions have a semantic that after the registration is done the object can be used and thus assigning private pointer afterwards is an error. Damn I didn't realize this in the nmve-fc review. -- Johannes Thumshirn Storage jthumshirn@xxxxxxx +49 911 74053 689 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
