[RFC] register_blkdev and unregister_blkdev

[BALBIR SINGH]

This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

I was looking at the code for register_blkdev and unregister_blkdev. I 
found that no
locking (spinlocks) are used to protect the blkdevs struture in these 
functions. I suspect
we have not seen a problem till now since

Either

1. register_blkdev is called from modules, and only module 
initialization is protected.
2. register_blkdev is called during init time for drivers in the kernel 
and I am not sure
    about whether calls to register_blkdev at this time are implicitly 
serialized, since only
    1 CPU is active during initialization

Anway, what I needed to know was if (1) and (2) are enough to ensure 
safety in register_blkdev
and unregister_blkdev.

May be I am missing something, there is already some lock which is held 
before these routines
are invoked, I could not find any.

Comments

Thanks,
Balbir Singh.

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain;
	name="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="Wipro_Disclaimer.txt"

----------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:[e-mail] and delete this mail
from your records.
----------------------------------------------------------------------------------------------------------------------

--------------InterScan_NT_MIME_Boundary--